Lines Matching refs:leap
85 * before the leap second is to be applied, but in practice at least some of
88 * instance->pp->leap indicator but only run this test in December and June for
107 * Luis Batanero Guerrero <luisba@rao.es> (Dec 2005) Patch for leap seconds
318 u_char count4; /* cycles thru leap after Gj to issue Bj */
2429 * Check the leap second status once per day.
2464 /* get leap-second warning message */
2470 * leap second will occur.
2488 instance->pp->leap = LEAP_ADDSECOND;
2489 cp = "Set pp.leap to LEAP_ADDSECOND";
2492 instance->pp->leap = LEAP_DELSECOND;
2493 cp = "Set pp.leap to LEAP_DELSECOND";
2497 instance->pp->leap = LEAP_NOWARNING;
2498 cp = "Set pp.leap to LEAP_NOWARNING";
2586 instance->peer->leap = LEAP_NOWARNING;
2587 cp = "Set peer.leap to LEAP_NOWARNING";
2590 instance->peer->leap = LEAP_DELSECOND;
2591 cp = "Set peer.leap to LEAP_DELSECOND";
2594 instance->peer->leap = LEAP_ADDSECOND;
2595 cp = "Set peer.leap to LEAP_ADDSECOND";
3228 /* There seems to be eternal confusion about when a leap second
3232 * get the actual leap second -- that is, the one that is
3237 * reflect the fact that it tells the second after the leap
3247 /* Only raise warning within a month of the leap second */
3249 instance->pp->leap = LEAP_NOWARNING;
3250 cp = "Set pp.leap to LEAP_NOWARNING";
3256 instance->pp->leap = LEAP_DELSECOND;
3257 cp = "Set pp.leap to LEAP_DELSECOND";
3259 instance->pp->leap = LEAP_ADDSECOND;
3260 cp = "Set pp.leap to LEAP_ADDSECOND";
3400 * Check the leap second status once per day.
3411 * As such, we have the workaround below, of only checking for leap