Hi, On Wed, May 12, 2010 at 11:39:31AM +0200, Michael Banck wrote: > I can reproduce this, just lost the db again after a kernel panic. > Personally, I would say having a persistent db across system issues is > pretty important for this kind of daemon, e.g. I'd like to have > statistics about which kernel has which uptime.
Maybe the default interval of writing the file once per minute is too excessive; AFAICT the code which writes the records does not run any fsync() (and does not check the errno after the fclose(), but that might be a side issue), so if the system crashes before the write buffers have been written to disk, who knows what happens with the old and new db. This should be coded much more robustely for something which tracks uptimes. Thanks, Michael -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
