tags 474500 moreinfo unreproducible
thanks

On Sun, Apr 6, 2008 at 10:36 AM, Peter Walser <[EMAIL PROTECTED]> wrote:
> Package: uptimed
>  Version: 1:0.3.10-3
>  Severity: normal
>
>
>  After more than 200 days running, the server power was shut off.
>  No big problem. After booting /var/spool/uptimed/records was gone
>  (or overwritten) and only the current boot is now visible.
>  Is the file opened at start and closed on normal shutdown
>  (whith start-stop-daemon)?

No. The records file is only open when necessary. The daemon doesn't
write directly to that file either. It writes to a temporary file and
then moves it in place of the old records file. I don't see how that
could lead to file corruption unless you've been unlucky enough to
kill power exactly at the moment of the update... Which leads me to
think that the default update interval of 60s is probably overkill and
prone to that kind of situation...

>  I suggest to open the file, write whatever and close immedately every time.

Which is exactly what is done, afaik.

>  Suggested cronjob workaround (not tested):
>  @daily  /etc/init.d/uptimed restart

How's that suppose to help?

Out of curiosity, what filesystem are you using on your system? In
particular what file system is used on /var/spool/uptimed ?



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to