Date: Fri, 04 Jan 2002 17:50:47 -0600 From: Christopher Schulte <schulte+freebsd@nospam.schulte.org> To: freebsd-questions@FreeBSD.ORG Subject: Re: clock problem Message-ID: <5.1.0.14.0.20020104174545.03fbdc90@pop3s.schulte.org> In-Reply-To: <200201042245.g04Mjat98429@lurza.secnetix.de> References: <5.1.0.14.0.20020104142346.03783678@pop3s.schulte.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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=20 cron. I prefer this method as one static crontab line keeps every system=20 on check. Since no clock will ever deviate by even a second between polls,= =20 I don't have to worry about sudden time changes. Reasonable? Sure. Elegant? Maybe not. Works? Yup! >Regards > Oliver --chris >-- >Oliver Fromme, secnetix GmbH & Co KG, Oettingenstr. 2, 80538 M=FCnchen >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?5.1.0.14.0.20020104174545.03fbdc90>