severity 504714 important
tags 504714 confirmed
thanks
On Thu, Nov 6, 2008 at 3:31 PM, Sylvain Veyri?
<[EMAIL PROTECTED]> wrote:
> (Hello Thibaud, comment ça va depuis le temps ?)
Ca va
> When the /var filsystem is full, uptimed, starting or stopping, makes
> the /var/spool/uptimed/records file become empty.
I'm tagging this as "important". It's indeed an unwanted behaviour,
but it doesn't render the package unusable for most of the users.
Plus, when /var is full, you have other (more important) problems than
simply loosing your uptimed db :-P
> 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.
a crash reboot history?? I don't think that's the purpose of uptimed.
There's wtmp ("last") for that.
Anyway, I believe that the patch I proposed for #482643 might be an
answer to that problem as well. Unfortunately nobody ever tried to
test it for now. It's likely gonna need an addtional check ("is the
record db empty") to fully address your bugreport.
CC'ing upstream maintainer.
HTH
--
Thibaut VARENE
http://www.parisc-linux.org/~varenet/
