On 11/8/2010 8:35 PM, Stephen Vaughan wrote:
Alright, I'll give it a miss then. We'll look into removing the locl clock.
Cheers,
Stephen
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On
Behalf Of Steve Kostecke
Sent: Monday, November 08, 2010 6:20 PM
To: [email protected]
Subject: Re: Local clock - sync issue
On 2010-11-08, Stephen Vaughan<[email protected]> wrote:
Yep it does work, I think that article I just posted is the fix.
Actually, that belongs in the Wiki as an example of what _not_ to do.
"burst" makes your ntpd poll the remote time server 8 times in rapid
sucession at each poll interval. Use of 'burst' against time servers
which you do not control (or don't have explicit permission from) is
considered to be unfriendly.
If you must use 'burst' to maintain sync then you have some network
issues which need to be addressed.
Perhaps he meant "IBURST"? That's certain allowable, particularly if he
does restarts at long (weeks or months) intervals. Given that NTPD
needs up to ten hours to get a tight lock on the correct time, most
users will want to minimize restarts.
_______________________________________________
questions mailing list
[email protected]
http://lists.ntp.org/listinfo/questions
