* toughguy [Thu, 20 May 2004 at 10:56 -0600]
<quote>
> I'd been having the same problem, even with CLOCK="local". It was something about
> Gentoo changing the clock time to compensate for time the computer had been off...I
> haven't rebooted into OSX yet to see if it worked, but here's what it was, if you
> want to try.
> Edit /etc/init.d/clock and comment out the line that says:
> errstr="$(/sbin/hwclock --adjust ${myopts} 2>&1 >/dev/hull)"
> For me it was on line 39.
</quote>Ah, yes, I remember back when I first started into Linux, there was that clock auto-correct thing. You would set the clock to an authoritative source, wait several days (the longer the more accurate) then see how far off the clock was from that same source. I think there was some script you gave the time to again, then it would calculate the difference and enter into some file how much to adjust the clock by per day or something. I thought it was really cool at the time, but I haven't seen it in ages. It looks like this is the kind of thing toughguy is talking about. It could also be an NTP thing going on. That could explain the problem popping up when it wasn't there before. Perhaps you installed something that depended on NTP and istalled a client for you (NTP == Network Time Protocol).
pgpsH4C2z8wKL.pgp
Description: PGP signature
____________________ BYU Unix Users Group http://uug.byu.edu/ ___________________________________________________________________ List Info: http://uug.byu.edu/cgi-bin/mailman/listinfo/uug-list
