On Tue, 2011-07-19 at 20:17 +0200, Max Kellermann wrote: > On 2011/07/18 23:53, Tibor Arpas <ti...@bidforfix.com> wrote: > > Please let the developers know if you need this functionality. Thanks a lot. > > We could store just the trace, or recover from the partial IGC file to > fill all the task engine internal variables (internal replay). > That'll take some CPU power, but we could skip the expensive > calculations, and only consider the ones that are important for > resuming the task after the crash. > If all you need to recover is the IGC log, so much the better, but how much faster than real-time can that be reread? That was one motivation for suggesting the use of a checkpoint file. The other was the possibility of automatically restarting the task after a crash, though of course a 'restart task' menu button is still needed to restart after a fat finger event.
Was I right to assume that the IGC log is written a buffer-full at a time? If so, XCSoar should still flush the buffer after rounding each waypoint, but I assume you already thought of that. Are there any other significant events that should force an fsync()? Martin ------------------------------------------------------------------------------ Magic Quadrant for Content-Aware Data Loss Prevention Research study explores the data loss prevention market. Includes in-depth analysis on the changes within the DLP market, and the criteria used to evaluate the strengths and weaknesses of these DLP solutions. http://www.accelacomm.com/jaw/sfnl/114/51385063/ _______________________________________________ Xcsoar-user mailing list Xcsoar-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xcsoar-user
