[ntp:questions] Re: NTP client configuration

Steve Kostecke kostecke at ntp.isc.org
Wed Oct 5 20:12:33 UTC 2005


On 2005-10-04, Resmi M R <resmi.nair at wipro.com> wrote:

> /etc/ntp.conf on server
> ------------------------
>
> server <server_ip address>

This should be the IP address of a remote time server, not the IP
address of the server that this ntpd is running on.

You should be using four, or more, remote time servers so that your ntpd
is able to detect, and ignore, false-tickers. And, for quicker initial
sync, append 'iburst' to your server lines.

> fudge <server_ip address> stratum 1

This line does nothing.

> server 127.127.1.0

Here you've told ntpd to use the undisciplined local clock (LocalCLK)
as a time source. It is considered to be a good practice to fudge the
LocalCLK to a stratum of 10 - 12 so that :

fudge 127.127.1.0 stratum 10

You should know that it will take ntpd as much as 10 minutes to become
"synchronized" to the local clock and be able to serve time to other
systems.

> broadcastdelay  0.008

This is not a part of your problem, but ...

You don't need to specify the broadcast delay unless you are using
broadcast / multicast mode.

> driftfile /etc/ntp.drift
> logfile /var/log/ntp.log

-- 
Steve Kostecke <kostecke at ntp.isc.org>
NTP Public Services Project - http://ntp.isc.org/




More information about the questions mailing list