[lug] Time zone grumbling
hugh at math.byu.edu
Fri Mar 31 15:20:10 MST 2006
> I didn't have to reboot (I stopped using Windows a long time ago because
> reboots should be every few months for hardware upgrades, not daily for poor
> OS implementation).
> ntpdate followed by hwclock --utc --systohc fixed my problem, thanks everyone!
> Still have one question, though... what is the difference between ntpdate and
> ntpd? I have read the man pages, but I still don't get it. For example, the
> ntpdate man page says:
> "ntpdate can be run manually as necessary to set the host clock, or it can be
> run from the host startup script to set the clock at boot time. This is
> useful in some cases to set the clock initially before starting the NTP daemon
> So does ntpdate set the correct time then ntpd keeps it there, or what? Why
> is ntpdate needed if you have ntpd?
Yup, ntpdate polls the ntp server and then just sets the clock. ntpd will
refuse to run if you are too far out of sync. ntpd will keep you within a
small delta of the time passed out by the server it queries.
More information about the LUG