On Thursday 12 June 2003 16:04, [EMAIL PROTECTED] wrote: > On Thu, Jun 12, 2003 at 03:54:40PM +0200, Paul de Vrieze wrote: > Content-Description: signed data > > > My understanding is that a combination of the two works well - and > that's reflected in the gentoo (and other distros) ntpd startup script: > > - ntpdate is a one-time setter that uses the protocol to determine > the current time. > > - ntpd is a daemon that uses the protocol to keep your clock honest. > > If your clock is way off, ntpdate changes it to the correct time without > complaint. If you start up ntpd and your clock is currently incorrect, > it'll correct a small error or give up on a large error. > > So the startup scripts do something that seems pretty reasonable: they > run ntpdate as you're booting, then start up ntpd. Seems to work pretty > well. >
That is correct. At bootup time no applications are running that would suffer from a time lapse, so then ntpdate is safe. Running ntpdate from a cronjob though, is not. Paul -- Paul de Vrieze Researcher Mail: [EMAIL PROTECTED] Homepage: http://www.cs.kun.nl/~pauldv
pgp00000.pgp
Description: signature
