[ntp:questions] leap second warning bits in practice

Miroslav Lichvar mlichvar at redhat.com
Wed May 13 09:03:47 UTC 2015

On Tue, May 12, 2015 at 11:33:31AM +0200, Marco Marongiu wrote:
> On 12/05/15 11:28, Marco Marongiu wrote:
> > Hi there
> > 
> > In http://doc.ntp.org/4.2.6p5/ntpd.html#leap I read: "If the leap is in
> > the future less than 28 days, the leap warning bits are set."
> > 
> > What are the practical consequences of the warning bits being set? Will
> > they cause the leap second to be armed in the kernel eventually? What if
> > the kernel discipline is disabled?
> To be a bit clearer, further down it says "When a majority of the
> survivors show warning, a leap is programmed at the end of the current
> month". What does that "programmed" stand for...?

I think it means setting of the leap status that's reported in NTP
packets and if the kernel discipline is enabled it also sets the
kernel leap status bits.

Miroslav Lichvar

More information about the questions mailing list