On Fri, Jun 29, 2012 at 5:26 PM, Hal Murray <[email protected]> wrote:
> > > Being an EDT/EST snob, I had my cron job all set for 11:59p tonight to > > record the leap second. But then reading an article today on the topic, > > I think "tonight" is a day early. The leap second happens at the end of > the > month, not early on the last day of the month. > > > > But now I'm wondering, will NTP pickup the change at 8:00p EDT? Or must > I > > do something to catch the change? > > It's all supposed to do the right thing, but nobody will be surprised if > there are glitches. > > The idea is that some GPS clocks and similar tell you a leap second is > coming. You can also get it from a file. On the last day of the month, > that > flag gets passed to the kernel and on to other NTP servers. If a server > sees > that the majority of the servers it is watching has their leap-pending flag > set, it will set it's flag and pass it on. > > You can check your server: > ntpq -c "rv 0 leap" $SERVER > > Looks like I'll see the leap change. [godzilla.empire.org(tcsh):6] ntpq -c "rv 0 leap" assID=0 status=44fd leap_add_sec, sync_uhf_clock, 15 events, event_13, leap=01
_______________________________________________ pool mailing list [email protected] http://lists.ntp.org/listinfo/pool
