On (13/05/05 00:04), Clive Menzies wrote: > On (12/05/05 16:59), Glenn English wrote: > > The system clock on one of my machines is running way slow. If I > > repeatedly run 'date' the second changes once every 3 or 4 seconds. > > ntpdate will bring it into line, but ntpd can't keep it there. > > > > I don't understand how this can happen. My experience with digital > > electronics says that things almost never work half-way; they're fine, > > or they're dead. Anybody know what the system clock actually is? A > > counter counting the line frequency?? A divider off the CPU clock? > > > > There was a power failure this morning, long enough to drain the UPSes > > and stop all the computers. Then when I started bringing things back up, > > I could just barely catch the aroma of overheated electronics -- so it > > could be hardware. It could also be my imagination. > > Can't help with the diagnosis but you're not the first on the list to > suffer time 'drift'. Solution: install something like 'ntpdate' to keep > the clock sychnronised with one of the internet time servers. FWIW > other people have recommended 'chrony' as an alternative - I've not tried > it. I'm just going outside to hit myself over the head with a hammer and repeat "I mustn't skim posts that I reply to".
Sorry ;) Clive -- www.clivemenzies.co.uk ... ...strategies for business -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
