Date: Tue, 23 Dec 2014 04:38:50 +0000 From: Jamie Landeg-Jones <jamie@dyslexicfish.net> To: freebsd-security@freebsd.org, cnehren+freebsd-security@pobox.com, brett@lariat.org Subject: Re: ntpd vulnerabilities Message-ID: <201412230438.sBN4coM8030741@dyslexicfish.net> In-Reply-To: <201412222323.QAA01574@mail.lariat.net> References: <252350272.1812596.1419241828431.JavaMail.zimbra@cleverbridge.com> <B6AF154A-FE22-4357-9031-91D661FD7E57@localhost.lu> <F7FACD2F-3AFE-4717-B4B9-B54A6FC70458@localhost.lu> <201412221745.KAA28186@mail.lariat.net> <20141222185238.GA3308@behemoth.lan> <201412222323.QAA01574@mail.lariat.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Brett Glass <brett@lariat.org> wrote:
> Within my own network, I have used cron and ntpdate (even though it's
> officially deprecated) on most of the clients, querying a couple of
I think ntpdate is only deprecated because it's functionality is provided
by 'ntpd -q'
> on them. But it obviously has some drawbacks; in particular, it doesn't
> continuously correct the clocks but makes them jump at particular
> times of day.
Until recently, I'd been using this too, however, using the '-B' option to
ntpdate ('-x' to nptd) to slew the clock instead. A couple of these a day in
cron causes neglegable drift, unless your clock ain't too good!
Cheers, Jamie
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201412230438.sBN4coM8030741>