Thibaut VARENE a écrit :
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
Yeah, that's true. But I thought the severity applies to the package itself.
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.
Huum I should have been more clear: I meant that uptimed is concerned by
reboots, reboots may be caused by crashes, crashes by full /var. So full
/var and uptimed business are not so far.
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.
OK, I'll try to find time to test your patch on the present bug, if it
does not need the additional check you mentionned. Unfortunately, I
don't think I will get enough to set up a crash test environment to
reproduce #482643 and test the patch.
Thanks,
Sylvain
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
