kosherkeron.blogg.se - Forum flightgear

#FORUM FLIGHTGEAR INSTALL#

Install FG 2017.1.2 which no longer uses a PID file for determining if two FlightGear instances are running (on MS Windows).

The problem with the read-only navigation cache on Windows is simple, and has been $FG HOME that is making the home directory read-only. I’ve just pushed a patch to next to change to a named-mutex-based solution on Windows (POSIX is unchanged), which can’t ever get stuck with stale data, since there is no file at all. However, it looks as if this behaviour may be fragile in the case of non-clean exits / power-offs. I then used Google / StackOverflow to find equivalent code for Windows - CreateFile with a ‘delete file on close’ flag. On POSIX I use standard open+unlink behaviour to create the PID file but ensure we don’t ever get stale ones, even if the system crashes. The actual problem seems to be the fgfs.pid file we use to ensure only one copy of FGFS is running with write-access to FG_HOME - all other copies run with read-only access.

(All of the above assuming we have found the solution, which is still uncertain but looking quite likely). It looks as if the whole nav-cache thing may have been completely mis-leading - the problem is nothing to do with the nav-cache at all, it’s unfortunate that the error mentioned it, since that has rather distracted from finding the solution. You can help the wiki by expanding it.īit of insight on the commonly reported failures on the forum about the Nav-cache being read-only.