Hi, 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.
nighthawk~$ ls -l /var/spool/uptimed/ total 12 -rw-r--r-- 1 daemon daemon 11 May 12 11:24 bootid -rw-r--r-- 1 daemon daemon 34 May 12 11:36 records -rw-r--r-- 1 daemon daemon 34 May 12 11:35 records.old ghthawk~$ grep root /etc/fstab /dev/mapper/nighthawk-root / ext4 relatime,errors=remount-ro 0 1 ghthawk~$ sudo grep -B3 clean /var/log/fsck/checkroot Wed May 12 11:24:26 2010 fsck from util-linux-ng 2.16.2 /dev/mapper/nighthawk-root: clean, 235402/610800 files, 1706305/2441216 blocks Michael -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
