Date: Fri, 12 Apr 2002 14:34:53 -0400 (EDT) From: <doug@safeport.com> To: "Bryan K. Ogawa" <bko@idiom.com> Cc: questions@freebsd.org Subject: Re: grr, stupid springforwardfallback (timed) Message-ID: <Pine.BSF.4.21.0204121423080.66738-100000@pemaquid.safeport.com> In-Reply-To: <200204121732.g3CHWlAd006668@baz.fake.primenet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I run the two on a my laptop because (a) my clock will drift by a large amount by the time I get on and off a plane, (b) I want to sync with my network wherever I may be, (c) using ntpdate only at boot works with no problems. The only hard thing to do was (is) figuring out the auth stuff (a work in progrress) so I do not have to do anything except connect when I travel. For the stationary systems it seems much more logical to run a single time server and sync the other hosts from that. On Fri, 12 Apr 2002, Bryan K. Ogawa wrote: > One option which avoids ntpd's vagaries (e.g. it complaining about > getting out of sync, and stopping working) is to run ntpdate out of > cron. I usually run it once an hour or so. > > -- > bryan k ogawa <bko@idiom.com> http://www.idiom.com/~bko/ > _____ Douglas Denault doug@safeport.com Voice: 301-469-8766 Fax: 301-469-0601 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?Pine.BSF.4.21.0204121423080.66738-100000>