[ntp:commitlogs] commit in whimsy.udel.edu:/deacon/backroom/ntp-dev

Harlan Stenn stenn at whimsy.udel.edu
Sat Aug 5 06:10:49 UTC 2006


stenn at whimsy.udel.edu fired the post-commit--009commitlogs trigger in /deacon/backroom/ntp-dev
    Committed the following deltas
    
    ======== ntpd/ntp_loopfilter.c ========
    D 1.124 2006/08/05 02:10:29-04:00 stenn at whimsy.udel.edu 131 130 22/22/1055
    P ntpd/ntp_loopfilter.c
    C Dave sez:
    C 
    C At cold start (no frequency file) the daemon sets the clock at the
    C first update, then waits 15 minutes, measures and corrects the
    C frequency (usually within 1 PPM) and assumes normal operation. This
    C saves many hours to converge the frequency within 1 PPM, especially
    C if the intrinsic frequency error is large, like 200 PPM.
    C 
    C Until the frequency is corrected, the machine can have serious
    C offset and frequency errors that would drive dependent clients nuts.
    C Up to now, the leap bits and stratum were not initialized until the
    C frequency was corrected. However, the clock was set and local clients
    C were free to believe or not believe the clock. After review, the
    C external behavior is only mildly worse than without the initial
    C training period, so the leap bits and stratum are now set at the
    C first update. The billboards should now be consistent with the
    C Principle of Least Astonishment.
    ------------------------------------------------
    ======== ntpd/ntp_proto.c ========
    D 1.246 2006/08/05 02:10:31-04:00 stenn at whimsy.udel.edu 309 308 19/15/3429
    P ntpd/ntp_proto.c
    C Dave sez:
    C 
    C At cold start (no frequency file) the daemon sets the clock at the
    C first update, then waits 15 minutes, measures and corrects the
    C frequency (usually within 1 PPM) and assumes normal operation. This
    C saves many hours to converge the frequency within 1 PPM, especially
    C if the intrinsic frequency error is large, like 200 PPM.
    C 
    C Until the frequency is corrected, the machine can have serious
    C offset and frequency errors that would drive dependent clients nuts.
    C Up to now, the leap bits and stratum were not initialized until the
    C frequency was corrected. However, the clock was set and local clients
    C were free to believe or not believe the clock. After review, the
    C external behavior is only mildly worse than without the initial
    C training period, so the leap bits and stratum are now set at the
    C first update. The billboards should now be consistent with the
    C Principle of Least Astonishment.
    ------------------------------------------------


More information about the commitlogs mailing list