James Turner wrote:
> On 14 Jan 2012, at 11:42, James Turner wrote:
>
>>> While trying to find out about a different issue ('fgfs' not starting
>>> at all) I noticed, that it still writes an "autosave.xml" into
>>> ${FG_ROOT} despite the fact that I've explicitly set
>>> --prop:/sim/startup/save-on-exit=false
>>> Now I'd like to learn wether someone is deliberately trying piss users
>>> off or it this is just a bug ;-)
>
> Just tested this and it seems to work for me (setting exactly that
> argument - there's also explicit options: --disable-save-on-exit and
> --enable-save-on-exit)
I just found out that I mixed $FG_ROOT and $FG_HOME. The "autosave.xml"
was written into $FG_HOME, not $FG_ROOT.
I typically set the properties directly via "--prop:/..." and I'm quite
sure that I picked the correct one because I matched it against
flightgear/src/Main/globals.cxx - and because I've been using
"/sim/startup/save-on-exit" successfully for ages to prevent FG from
creating a $HOME/.fgfs/ directory.
BUT, with a new build from todays GIT the "autosave.xml" doesn't get
written any more. Maybe it's been linked to the recent relative path
changes.
Anyhow, two directories are still being created in ${FG_HOME}, which
are "ai" and "Export". Is it supposed to be permitted for an FG
instance to write into the install dir ?
Cheers,
Martin.
--
Unix _IS_ user friendly - it's just selective about who its friends are !
--------------------------------------------------------------------------
------------------------------------------------------------------------------
RSA(R) Conference 2012
Mar 27 - Feb 2
Save $400 by Jan. 27
Register now!
http://p.sf.net/sfu/rsa-sfdev2dev2
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
