> BIOS clocks are uncompensated, unadjusted drifty cheap thingies need
> ntpd to tame them.

Also try "man adjtimex" - since the BIOS clock is only used when the PC
is off and Linux controls time when the PC is running, adjtimex will
synchronise with an NTP server as a one-off and then adjust the speed of
the kernel clock to keep it running much more precisely. I've got the
clocks on my PCs accurate enough now that after running for one month
24/7 they're all only out by about one second or so...

> > Great UPS besides this battery dieing on me. It has served me well
> > for 4+ years of 24/7 use. I got it on sale for cheap. Belkin has a
> > "blowout" sale about once

Well just in case someone's ever Googling on this thread, I had a very
similar problem to this only without the UPS. It turned out that the
motherboard connector in the ATX power supply was a little loose, and
this would cause the PC to shut down and/or restart for no reason. A
screwdriver to bend the pins a little so they're a bit tighter was all
that was needed to fix that annoying issue!

Cheers,
Adam.

MikeReynolds <mreynolds@invalid.com> wrote:
> anything usefull. (No errors or any other obvious failures for the reboot) I
> also checked faillog, but it seems to be a binary file. Not quite sure why.

/var/log/faillog is read by the (superuser) "faillog" command and
only stores info about FAILed LOGin attempts (from text mode, kdm/xdm
etc do not store this info).
--
************************************************** ******************
** Eef Hartman, Delft University of Technology, dept. EWI/TW **
** e-mail: E.J.M.Hartman@math.tudelft.nl, fax: +31-15-278 7295 **
** snail-mail: P.O. Box 5031, 2600 GA Delft, The Netherlands **
************************************************** ******************