Enrico wrote: > * Harlan Stenn <[email protected]> wrote: > > > Just to be clear, there *used* to be some reasons to set the clock > > before starting ntpd. In general, there is no need to do this anymore > > and I have not heard any good reasons it should still be needed. > > > > If anybody knows of any *good* reasons to set the clock before starting > > ntpd, please speak up. > > Indeed! > It is very handy to set the clock directly on system startup > (eg. when the external clock is lacking proper battery). > I've still got a bunch of system using it. > > Oh, and of course its very handy for diagnostics.
I'm not saying one should not set the clock on system startup. I'm saying I'm not aware of good reasons to set the clock before starting ntpd at system startup. Again, from what I have seen, BCP (Best Current Practice) is to start ntpd as early as possible in the boot sequence, and then as late as possible in the boot sequence run something like ntp-wait before starting time-sensitive startup-processes and opening the system to general use. With a good drift file and a proper ntp.conf file, ntpd will have the clock fully sync'd in about 11 seconds' time. If ntpd should step the time during this startup phase, it will log to syslog and to utmp/wtmp (as appropriate). Debugging based on log timestamps during startup is pretty easy. H _______________________________________________ questions mailing list [email protected] http://lists.ntp.org/listinfo/questions
