Dave, Thanks for those pointers. I realize now that I misunderstood the hwclock man page and thought the only way for the adjustments to take effect was manually (or via a cron job or equivalent). That didn't seem much better than NTP to me at the time so I went ahead and set up xntpd instead (fortunately, my DSL connection is up 24/7 so I can run this without any pain and suffering). NTP is working well so far but I still can't get over the feeling that something else is wrong and this is just a hack. I couldn't find any SuSE RPMS for adjtimex but it looks like every other PPC distribution has one. I guess I should look into that option more in case it is a little cleaner. Thanks again, Ron On Fri, Feb 15, 2002 at 09:24:24PM -0700, Dave Gomez wrote:
Ron, I was just brushing up on the subject against the mini-howto, http://www.ibiblio.org/pub/Linux/docs/HOWTO/mini/other-formats/ html_single/Clock.html Or for all http://www.linuxdoc.org/, and the jist of it was, at startup, linux copies the time in the hardware clock to the system clock in memory, which runs off a timed software routine to keep the clock on time. It never references the hwclock again, unless a startup occurs, or manual intervention takes place. Adjtime allows you to give the software clock a tweak factor if for some reason the software drumbeat is not timed right, interjecting a correction factor.
Hope that helps, Dave Gomez