1
Note that ntpdate is run during system startup. If you specify
2
servers that are not reachable at boot time, you'll have to wait for
3
ntpdate to time out looking for them. In this case, you might want to
4
consider editing /etc/init.d/ntpdate to comment out the invocation
5
there, and add a fragment to your ppp/isdn/whatever startup scripts
8
Also, note that ntpdate is *not* really intended to be used by servers with
9
good network connectivity. The 'ntp' package, which provides a persistent
10
daemon that does a better job of keeping system time than even a cron'ed
11
invocation of ntpdate, is a better choice for systems with good network
12
connectivity. It may be useful to also have ntpdate on systems that run
13
ntp, so that the clock is warped to approximately the right time at boot
14
before ntp is launched, but there are options to ntpd that can be added to
15
the init.d script for the ntp package that can accomplish much the same
1
ntpdate doesn't parse the /etc/ntp.conf file. The program
2
ntpdate-debian is provided that reads its server list from
3
/etc/default/ntpdate or alternatively from /etc/ntp.conf.
5
ntpdate is run whenever a network interface is brought up. To adjust
6
this behavior, the file /etc/network/if-up.d/ntpdate should be edited.
8
Note that ntpdate is *not* really intended to be used by hosts with
9
good network connectivity. The "ntp" package, which provides a
10
persistent daemon that does a better job of keeping system time than
11
even a cron'ed invocation of ntpdate, is a better choice for systems
12
with good network connectivity. If all you want is to set the clock
13
to a reasonable value once in a while, a more light-weight package
14
like "rdate" can also do the job.