At 12:18 AM 12/1/99 -0800, Todd A. Jacobs wrote:
>My system clock always reads 30 minutes fast after a reboot. I set my
>system clock daily using rdate, followed by setclock to set the hardware
>clock. I don't experience any significant time slippage when the system is
>running normally. However, after any reboot, the time is always around 30
>minutes fast.
>
>Other than a bad battery, what could account for this behavior?
Lots of people have similar trouble. I've never figured this out. It
seems to revolve (i.e., for me and these others) around the difference
between local time and UTC. So if you're not -.5 or +.5 then maybe I'm
off-base. Something likes to revert. I'd love to know what but I've never
had the spare time to worry. Instead, when it's important, I kludge things
by using a cron job to rdate periodically. You could also do this in
rc.local to get it at boot-up too. This will screw up some processes that
worry about exact times, so be careful.
Something like:
------8< cut here 8<-------
#!/bin/sh
#the NIST computer is sometimes unreachable... sync first to a local host
/usr/bin/rdate -s sparkle.soltec.net
#on an hourly basis, sync to the NIST time machine
/usr/bin/rdate -s time.nist.gov
------8< cut here 8<-------
-Alan
---
Alan D. Mead / Research Scientist / [EMAIL PROTECTED]
Institute for Personality and Ability Testing
1801 Woodfield Dr / Savoy IL 61874 USA
217-352-4739 (v) / 217-352-9674 (f)
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
