I typically string 3 or four servers coupled by &&'s in case one of the servers is down. For example... ntpdate time.nist.gov && ntpdate for.a.good.time.call.gov && ntpdate time.enough.org I have found that time servers are not always responsive and the above works around that. Another problem I've run into (although I've not researched it) is that ntpdate seems to fail when the system time is several years off. Kent "Thomas T. Veldhouse" wrote: > > ntpdate adjusts the speed of the clock. This avoids problems with changing > the time. It recommends that you run ntpdate every hour or two. I chose > every two as my time does not drift much at all. > > Tom Veldhouse > veldy at veldy.net > > ----- Original Message ----- > From: "Mark K" <mkroska at readynetgo.com> > To: <tclug-list at mn-linux.org> > Sent: Friday, November 10, 2000 10:14 AM > Subject: Re: [TCLUG:23670] keeping time correct > > > > > I use a 1 liner in /etc/cron.weekly/ to keep things "timely" here. The > > gov't server is as accurate as I feel necessary: > > rdate -s time.nist.gov > > and set the perms to 770, owned by root, good to go! > > You could of course run it daily, but weekly seems frequent enough. > > > > MK > > > (trimmed)