Date: Tue, 21 Apr 2009 11:43:39 -0700 From: Chuck Swiger <cswiger@mac.com> To: Mel Flynn <mel.flynn+fbsd.questions@mailing.thruhere.net> Cc: freebsd-questions@freebsd.org Subject: Re: Preventing ntpd from adjusting time (backwards) Message-ID: <BCF242F6-FF5E-4A5D-BA4B-E1A8F7F0A41B@mac.com> In-Reply-To: <200904212033.51524.mel.flynn%2Bfbsd.questions@mailing.thruhere.net> References: <200904211106.01965.mel.flynn%2Bfbsd.questions@mailing.thruhere.net> <200904212023.14365.mel.flynn%2Bfbsd.questions@mailing.thruhere.net> <344D9702-C894-4E54-B256-43FAB17903F1@mac.com> <200904212033.51524.mel.flynn%2Bfbsd.questions@mailing.thruhere.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Apr 21, 2009, at 11:33 AM, Mel Flynn wrote: > On Tuesday 21 April 2009 20:29:18 Chuck Swiger wrote: >> On Apr 21, 2009, at 11:23 AM, Mel Flynn wrote: >>> Now I'm also wondering how ntpd handles securelevel 2. >> >> "man init" suggests that stepping the clock by more than a second is >> disallowed: > > yes, so does it bail or retry till skew wins over the failed steps? The attempt to step the clock will fail. ntpd should continue to run, but the rate of skewing is typically limited to 1 second of correction over a time interval of 2000 seconds. If your clock routinely drifts by more than 1 second every hour or so, ntpd is unlikely to be able to correct the time at all under securelevel 2. If your clock drift is less, ntpd should eventually manage to sync time, but for extreme cases, running ntpdate periodically to forcibly reset the clock might be needed (and to run ntpdate after boot, you'd need to back down to securelevel 1). Regards, -- -Chuck
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BCF242F6-FF5E-4A5D-BA4B-E1A8F7F0A41B>