I was wondering what others think about handling leap seconds when ntpd is running in the "slew only" mode (-x option).
The -x option disables the kernel discipline, so the kernel is not told about pending leap seconds and its up to ntpd to do whatever is needed. Older ntpd versions (before 4.2.6) didn't handle leap second in the daemon loop and -x could be used to avoid the backward step in the Unix time scale and possibly upset the applications running on the system. In 4.2.6 was added support for leap seconds in the daemon loop and ntpd now steps the clock by calling settimeofday() or clock_settime(), even if the step threshold (set by -x or tinker step) is larger than one second. Should be leap seconds threated as a normal offset and not corrected by step when the threshold is larger than 1.0? Should there be a separate option for them? http://bugs.ntp.org/show_bug.cgi?id=2745 -- Miroslav Lichvar _______________________________________________ questions mailing list [email protected] http://lists.ntp.org/listinfo/questions
