Scenario: Terrasync is running. FG is running. FG exits.
New copy of FG starts. Terrasync says, quote
pos in msg = -9999,-9999
lat = -9999 lon = -9999
lat_dir = -1 lon_dir = -1
FlightGear is not running, exiting.
That seems a bit strange.
*) FG should not send a bogus lat/lon.
*) Given an obviously bogus lat/lon, terrasync should not
do anything, let alone exit.
*) "FlightGear not running" should not be a reason for
terrasync to exit.
*) What's with the bare linefeeds?
*) There should be an easy way of determining if terrasync is
or is not already running, so scripts can determine if it
is necessary to start one, and avoid starting a second copy.
There are ways of figuring this out using netstat, but a
simpler way would be more user-friendly. Perhaps terrasync
itself could check. Perhaps terrasync could write its pid
to a file such as terrasync-5500.pid in some suitable
directory.
------------------------------------------------------------------------------
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing.
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev
_______________________________________________
Flightgear-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
