In response to John Webster <[EMAIL PROTECTED]>:
> --On December 21, 2007 11:23:03 AM -0500 Bill Moran <[EMAIL PROTECTED]> wrote:
> > In response to shinny knight <[EMAIL PROTECTED]>:
> > The reason that is not recommended is that it results in sudden steps
> > of the clock. Occasionally, these steps go backwards. Software that
> > is very sensitive to time changes (make processes, database servers,
> > anything doing calculations WRT time) can break, crash, or work
> > inaccurately.
> ntpdate -B should slew the time slowly. (According to the manpage.)
Not generally suitable for cron because it can take longer to slew
than it does for the next cron execution to occur, which would then
result in multiple ntpdate programs fighting each other (not sure
what the effect of this would be).
If you ask me, the -B option is available for people who want to
totally hose timekeeping on their system.
email@example.com mailing list
To unsubscribe, send any mail to "[EMAIL PROTECTED]"