Mauro wrote:
> What's the difference of running ntpdate instead ntp with cron?
'ntpdate' jumps the clock. It was intended for use at system boot
time when that is okay to do. 'ntpd' is a daemon that runs and makes
small clock adjustments as needed to keep time without "jumping" it.
The 'ntpdate' command is now deprecated. It's functionality has been
written into the ntp daemon code. The ntpd daemon now has ntpdate
functionality with:
$ man ntpd
-g Normally, ntpd exits with a message to the system log if the offset
exceeds the panic threshold, which is 1000 s by default. This
option allows the time to be set to any value without restriction;
however, this can happen only once. If the threshold is exceeded
after that, ntpd will exit with a message to the system log. This
option can be used with the -q and -x options.
-q Exit the ntpd just after the first time the clock is set. This
behavior mimics that of the ntpdate program, which is to be
retired. The -g and -x options can be used with this option.
Note: The kernel time discipline is disabled with this option.
Running ntpd to adjust the clock continuously is much better than
jumping the clock with ntpdate.
Bob
Attachment:
signature.asc
Description: Digital signature