Package: uptimed Version: 1:0.3.12-2 Severity: grave Justification: causes non-serious data loss
(Hello Thibaud, comment ça va depuis le temps ?) When the /var filsystem is full, uptimed, starting or stopping, makes the /var/spool/uptimed/records file become empty. For stop-daemon, I think it succeeds to create records.tmp file, fails to put data on it, then copy this corrupted file to replace the correct records file. Note there is the same problem at start-daemon. I have reproduced this bug from scratch on another machine with up-to-date lenny: 1) make /var full 2) uprecords (we see current uptime and all older ones) 2) #/etc/init.d/uptimed stop 3) #uprecords (now only current uptime) My /var is an ext3 filesystem on both machines (second one over lvm). This is a problem: we can accept that uprecords and uptimed work wrongly when /var is full (like make wrong reports), but not a data loss that is not recoverable without backup (thanks amanda). As uptimed is useful to have a "crash reboot history", and as a crash issue may be caused by a full filesystem, I think this is a grave issue for this package. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (800, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-1-amd64 (SMP w/2 CPU cores) Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/bash Versions of packages uptimed depends on: ii debconf [debconf-2.0] 1.5.22 Debian configuration management sy ii libc6 2.7-15 GNU C Library: Shared libraries ii libuptimed0 1:0.3.12-2 Library for uptimed uptimed recommends no packages. uptimed suggests no packages. -- debconf information: uptimed/mail/do_mail: Never uptimed/mail/address: [EMAIL PROTECTED] uptimed/interval: 60 uptimed/mail/milestones_info: uptimed/maxrecords: 50 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
