Date: Thu, 18 May 2000 06:18:28 +1000 From: Peter Jeremy <peter.jeremy@alcatel.com.au> To: Harlan Stenn <Harlan.Stenn@pfcs.com> Cc: freebsd-stable@FreeBSD.org Subject: Re: Flag for NTP slew only? Message-ID: <00May18.061829est.115213@border.alcanet.com.au> In-Reply-To: <9760.958147629@brown.pfcs.com>; from Harlan.Stenn@pfcs.com on Sat, May 13, 2000 at 02:10:49AM %2B1000 References: <B500F74C6527D311B61F0000C0DF5ADC263081@valhall.ign.se> <9760.958147629@brown.pfcs.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, May 13, 2000 at 02:10:49AM +1000, Harlan Stenn wrote: >I believe ntpdate will not be around for much longer I'm intrigued by this comment. The [x]ntp documentation has traditionally listed two major uses for ntpdate: 1) "ntpdate -b" early in the boot process to get the system clock almost right - avoiding xntpd's fairly slow lock-in time and ensuring that there's no need for a time step once the system is running. ntpd may synchronise much faster than xntpd did, but the system will still be well into multi-user mode before it realises that the clock needs to be stepped by a (possible significant) amount. 2) Regular use of ntpdate (eg from cron) to keep the system clock fairly close to real time without the overheads of permanently running nptd. Whilst this is less of an issue for modern systems, people may still have reasons for not wanting to run ntpd. How will these functions be handled in the absence of ntpdate? Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?00May18.061829est.115213>