Quote: Originally Posted by
eurocarpc 
Heyaaa!! I've just come to an idea: how about a 'watch -n 1 du -hs .googleearth/' until it gets to 2000MB and stopping/doing something else then?
I'm doing it right now to monitor how fast it works (about 1MB every ten/twenty seconds, under not very populated areas) =)
On the other hand, it sometimes gives an unclosed token error if the refresh rate is too high -below 5 secs- specially if under places not even partially cached and with a lot of information to display.
Is there any way to handle that?
Oh! And... does it make any difference in terms of caching speed if GE is minimized or not? (Given that my cpu never reaches 100% load, that I've got 2GB RAM and a X1400 Graphics card)
Well... thanks again!
No problem, glad it's working. Good idea on watching the cache.
Usually, hitting "ignore" will stop prompting after an error. I've tried a few ways around this (but haven't followed up in awhile), but basically what is happening is that it's reading the KML file while it's being written to. Apparently GE doesn't pay attention to file locking.
This is also a problem with my GE GPS gpsd tracker. One solution I tried was instead of using a file, using a network resource, having the program fork a mini http server, but even then it sometimes glitches, as sometimes it doesn't wait for the response, which is weird as the time we are talking about is a fraction of a second.
I'll take another look at it soon when I have a bit more time.
Linear Mode
