That is that way I understood it. I never did try try ntpd and with ntpdate in my local.start. That probably would have corrected my problems, but ntpdate seems to be working fine by itself right now. Interesting conversation on the subject though. Dave > > > > I don't know but the use of ntpd is to be prefered over ntpdate as ntpd > > prevents time lapses, or even double occurence of the same time, which > > can be a cause of problems in compilation (makefiles rely on good times). > > 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. > > Nathan Meyers > [EMAIL PROTECTED] > > -- > [EMAIL PROTECTED] mailing list
-- [EMAIL PROTECTED] mailing list
