mirror of
https://github.com/FEX-Emu/FEX.git
synced 2026-10-10 23:00:30 +02:00
On an overburdened system then FEXMountDaemon may notrespond within the two seconds of FEX waiting for an ack. In this case then we hit a bad edge case where we overwrite the lock file with a new FEXMountDaemon instance then spin up a new FEXMountDaemon. This new FEXMountDaemon will recognize that one is still running and early exit, but now that we've overwritten the lock file with a new location, all future FEX instances won't be able to find the squashfs rootfs. Instead, ignore that the ack wasn't received and attempt running instead. FEXMountDaemon should still pick up the pipe message and monitor FEX regardless. This fixes the `/usr not found` messages and crashes resulting from it.