20,741
edits
Fgfs.pid: Difference between revisions
Jump to navigation
Jump to search
m
no edit summary
(Created page with "{{Stub}} <code>fgfs.pid</code> the stale ''fgfs.pid'' file for making a second FG instance read-only. This is now well known to the FG developers. It has absolutely nothing...") |
mNo edit summary |
||
| Line 2: | Line 2: | ||
<code>fgfs.pid</code> | <code>fgfs.pid</code> | ||
the problem with the read-only navigation cache on Windows is simple, and has been [[$FG HOME|$FG HOME]] that is making the home directory read-only.</li><li> Install FG 2017.1.2 which no longer uses a PID file for determining if two FlightGear instances are running (on MS Windows).</li><ref>{{cite web | |||
|url = https://forum.flightgear.org/viewtopic.php?p=306460#p306460 | |||
|title = <nowiki> Re: Flightgear won't open </nowiki> | |||
|author = <nowiki> bugman </nowiki> | |||
|date = Mar 6th, 2017 | |||
|added = Mar 6th, 2017 | |||
|script_version = 0.36 | |||
}}</ref> | |||
This issue is due to a stale ''fgfs.pid'' file in [[$FG HOME|$FG HOME]] on certain MS Windows systems which makes $FG_HOME partly read-only, blocking TerraSync from downloading and disallowing the saving of the new, version specific navigation cache SQL database after an upgrade (hence FG cannot start). This long standing bug has been [https://sourceforge.net/p/flightgear/mailman/flightgear-devel/thread/EBE91A6C-23F6-421E-9B22-D3A799B53438%40mac.com/#msg35691413 permanently fixed] in the latest 2017.1.2 release.<ref>{{cite web | |||
|url = https://forum.flightgear.org/viewtopic.php?p=306297#p306297 | |||
|title = <nowiki> Re: sql: attempt to write a read only database </nowiki> | |||
|author = <nowiki> bugman </nowiki> | |||
|date = Mar 4th, 2017 | |||
|added = Mar 4th, 2017 | |||
|script_version = 0.36 | |||
}}</ref> | |||
This issue is mainly due to a stale ''fgfs.pid'' file in [[$FG HOME|$FG HOME]] on certain MS Windows systems which makes $FG_HOME partly read-only, blocking TerraSync from downloading. This has been [https://sourceforge.net/p/flightgear/mailman/flightgear-devel/thread/EBE91A6C-23F6-421E-9B22-D3A799B53438%40mac.com/#msg35691413 permanently fixed] in the latest 2017.1.2 release. | |||
<ref>{{cite web | |||
|url = https://forum.flightgear.org/viewtopic.php?p=306232#p306232 | |||
|title = <nowiki> Re: terrasync not working </nowiki> | |||
|author = <nowiki> bugman </nowiki> | |||
|date = Mar 3rd, 2017 | |||
|added = Mar 3rd, 2017 | |||
|script_version = 0.36 | |||
}}</ref> | |||
the stale ''fgfs.pid'' file for making a second FG instance read-only. This is now well known to the FG developers. It has absolutely nothing to do with the navigation cache SQL database, but this error message threw the developers off-track for the 1-2 years the bug has existed. Deleting any ''navdata_*.cache'' files has no effect. This has been permanently fixed in FG 2017.1.2, as the PID file is no longer used. | the stale ''fgfs.pid'' file for making a second FG instance read-only. This is now well known to the FG developers. It has absolutely nothing to do with the navigation cache SQL database, but this error message threw the developers off-track for the 1-2 years the bug has existed. Deleting any ''navdata_*.cache'' files has no effect. This has been permanently fixed in FG 2017.1.2, as the PID file is no longer used. | ||