[ntp:questions] Linux client ntp
castellani.riccardo at tiscali.it
Sun Apr 22 10:04:35 UTC 2007
Why should I have to use iburst option in server command to speed up ?
when is the "iburst" option necessary ?
----- Original Message -----
From: Steve Kostecke
To: questions at lists.ntp.isc.org
Sent: Monday, April 16, 2007 1:33 PM
Subject: Re: [ntp:questions] Linux client ntp
On 2007-04-16, castellani.riccardo at tiscali.it wrote:
>Steve Kostecke said:
>>>Ricardo Castellani said:
>>> IPv4: restrict x.y.z.w [nomodify notrap nopeer noquery]
>>> If added "nomodify" option(as I told you in previous message) I
>>> think it would not be permitted to ntpd to use time information
>>> (sent from specified "x.y.z.w" server) to set local clock.
>> No, 'nomodify' has nothing to do with time service.
> Steve thanks for your full explanation. So, if I have in my client's
> restrict default nomodify notrap nopeer noquery
> server A
> server B
> I'm able to accept time from both server A and server B ? it's OK ?
Yes. None of those access control options will prevent time service.
All of these options are documented at
If you will be running ntpd as a daemon you should append 'iburst' to
each of your server lines. This will speed up your initial sync from
~5 minutes to ~20 seconds. Please remember that 'iburst' has no effect
Steve Kostecke <kostecke at ntp.isc.org>
NTP Public Services Project - http://ntp.isc.org/
questions mailing list
questions at lists.ntp.isc.org
More information about the questions