Re: setting hardware clock from NIST
brownh@hartford-hwp.com (Haines Brown) writes:
>> From: David Z Maze <dmaze@debian.org>
>
>> It's almost certainly better to find a local time server and not
>> hammer on the NIST's; I'd also use ntp (ntp-simple package) to keep
>> your clock up-to-date while the system is running.
...
> Thanks for the advice. I normally don't reboot for months at a time,
> and so need to sync clocks with cron. I'll kill the symlink in
> /etc/rc2.d. I assume that /usr/sbin/ntpd is the executable that I
> should symlink in /etc/cron.daily.
If you install ntp-simple it will start a daemon that will
periodically poll the time servers and gently keep your clock in
sync. (If you're five seconds off, that time will be made up
gradually, rather than abruptly shifting the clock.) No need to set
up a cron job.
> In reading the doc, I see that ntpq, run without argument, is a way
> to do a simple test of ntp functionality. However, that does not
> seem to be part of the ntp-simple package, nor is it itself a
> package. Have you used ntpq, and if so, how?
It's in the base ntp package, which is suggested by ntp-simple. For
looking at my own ntp daemon, 'ntpdc -s' will give you a short summary
of what other time daemons you're talking to, and 'ntptrace' will show
the synchronization chain from yourself to a stratum-1 time server.
--
David Maze dmaze@debian.org http://people.debian.org/~dmaze/
"Theoretical politics is interesting. Politicking should be illegal."
-- Abra Mitchell
Reply to: