Erik Hofman wrote:
Harald JOHNSEN wrote:
Another problem not related to pure performance is that the first
retrieval of metar data can block FG for a long time (perhaps one
minute) when the metar server is not accessible (or when there is any
network problem). The code does a lot of (useless) retries. Perhaps
its simpler not to update the metar on IO error and continue silently.
Which version of FlightGear are you using?
This has been fixed a long time ago.
Erik
_______________________________________________
Flightgear-devel mailing list
[email protected]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
I've just looked at the code. I see that the error count is incremented
in the catch but I think I don't enter here, I am spamed with 'metar
data too old' on the console. After some time I have a real socket error
and I think that after that I enter the catch statement and the error
counter is finaly incremented ! Strange that the increment is inside the
#ifdef threads.
So to be clear :
1) I have a lot of 'metar too old' message (no log file but its more
than 50 per loop)
2) after some time I have a sigio (if I remember well, that does not
happens everyday of course)
3) repeat 3 times
Its with cvs version and that happens in the init code.
Harald.
_______________________________________________
Flightgear-devel mailing list
[email protected]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
