Date: Thu, 06 Apr 2000 20:10:37 -0500 From: David Kelly <dkelly@hiwaay.net> To: Freebsd Questions <freebsd-questions@FreeBSD.ORG> Subject: Re: Best Time Synch Utility Message-ID: <200004070110.UAA11611@nospam.hiwaay.net> In-Reply-To: Message from Ben Smithurst <ben@scientia.demon.co.uk> of "Thu, 06 Apr 2000 16:45:48 BST." <20000406164548.E39831@strontium.scientia.demon.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
Ben Smithurst writes: > Bhishan Hemrajani wrote: > > > I prefer xntpd as you don't have to run it periodically, it will > > automatically update. > > You should remember than not everyone has the luxury of a 24/7 Internet > connection, and ntpdate is much more convenient in that case. So? As long as you filter the ntp port(s) so your auto-dial ppp connection isn't activated then ntpd (and xntpd previously) works fine. When the connection resumes, the daemon syncs. Meanwhile it works on calibrating your system clock and applies this calibration whenever the daemon is running, connected or not. Put something like this in your ntp.conf file: # Write clock drift parameters to a file. This will allow your system # clock to quickly sychronize to the true time on restart. driftfile /etc/ntp.drift -- David Kelly N4HHE, dkelly@hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200004070110.UAA11611>