fbsd-x at packet.org.uk
Mon Jul 21 08:22:35 BST 2003
* Matthew Seaman <m.seaman at infracaninophile.co.uk> [2003-07-19 13:10:10 BST]:
> On Sat, Jul 19, 2003 at 11:18:41AM +0100, Gavin Davenport wrote:
> > I'm doing that - every 10 minutes
> > By which time the clock reset is ~ -174 seconds.
> > Any idea why the system clock has gone so bananas ???
> > -----Original Message-----
> > From: Peter McGarvey [mailto:fbsd-x at packet.org.uk]
> > Sent: 19 July 2003 11:14
> > To: Gavin Davenport
> > Cc: freebsd-users at uk.freebsd.org
> > Subject: Re: NTP problems
> > Hmmm, if all you want to do is keep your clock correct, and (as included
> > config mentions) you've got a timeserver nearby, why not simply add
> > ntpdate ntp
> > in /etc/crontab?
> Where does this pernicious idea that running ntpdate(8) out of cron is
> such a good way to keep a clock in synch come from?
Well, if running ntpdate from cron really is "very harmful", as you
suggest, then perhaps you'd like to explain why.
But in answer to your question see the ntpdate(8) man page.
Freelance FreeBSD Hacker
(will work for bandwidth)
More information about the Ukfreebsd