Date: Sat, 5 Jan 2002 01:22:54 +0100 (CET) From: Oliver Fromme <olli@secnetix.de> To: freebsd-questions@FreeBSD.ORG Subject: Re: clock problem Message-ID: <200201050022.g050Msf03350@lurza.secnetix.de> In-Reply-To: <5.1.0.14.0.20020104174545.03fbdc90@pop3s.schulte.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Christopher Schulte <schulte+freebsd@nospam.schulte.org> wrote: > At 11:45 PM 1/4/2002 +0100, Oliver Fromme wrote: > >Christopher Schulte <schulte+freebsd@nospam.schulte.org> wrote: > > > You can cron `ntpdate` to update the clock every minute. > > > > Much more reasonable would be to run ntpdate once during > > boot and then run the ntpd daemon. Do not run ntpdate with > > cron. > > I have a central ntp server on my network, by which all hosts ntpdate via > cron. I prefer this method as one static crontab line keeps every system > on check. Since no clock will ever deviate by even a second between polls, > I don't have to worry about sudden time changes. > > Reasonable? Sure. Elegant? Maybe not. Works? Yup! I disagree. Running ntpd has a lot of advantages, and I don't see a single advantage in running ntpdate via cron once per minute. This is just terribly inefficient and can cause subtle problems, in particular when one of the clocks really dies. And when your NTP server is offline for some reason, the clocks start diverging much faster. Regards Oliver -- Oliver Fromme, secnetix GmbH & Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "All that we see or seem is just a dream within a dream" (E. A. Poe) 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?200201050022.g050Msf03350>