No booze.. aargh! Have to make do with monitoring. As one experiment, I have just installed .8p3 on a BBB to see what a smeared LS looks like. Seems to be working. Or at least doing something.
mike@bb2:~/src/python$ ntpq -c rv bb1 associd=0 status=4619 leap_add_sec, sync_ntp, 1 event, leap_armed, version="ntpd [email protected] Tue Jun 30 16:13:35 UTC 2015 (1)", processor="armv7l", system="Linux/3.8.13-bone47", leap=01, stratum=2, precision=-19, rootdelay=0.606, rootdisp=6.423, refid=192.168.1.4, reftime=d93d6d9a.0ab325f9 Tue, Jun 30 2015 19:33:46.041, clock=d93d6e92.ea82989e Tue, Jun 30 2015 19:37:54.916, peer=51860, tc=6, mintc=3, offset=-0.003556, frequency=-30.188, sys_jitter=0.055002, clk_jitter=0.017, clk_wander=0.005, tai=35, leapsec=201507010000, expire=201512010000, leapsmearinterval=21600, leapsmearoffset=-171.641 mike@bb2:~/src/python$ ntpdate -d bb1|grep adjust host found : bb1.stratum1.d2g.com 30 Jun 19:39:01 ntpdate[9545]: adjust time server 192.168.1.30 offset -0.175234 sec We'll see how it goes. Le 30.06.2015 15:51, Poul-Henning Kamp a écrit : > -------- > In message <[email protected]>, Rob Seaman writes: > >> What are people's plans for the day? > > I'm setting up as much of my usual data collection as I can get to > work, in order to have and provide test-data for tests of leap-second > handling. > > It doesn't look like I'll get my VLF sampler running though. > > Previous leapsecond data: > > http://phk.freebsd.dk/Leap/20081231/ [1] > > http://phk.freebsd.dk/Leap/20051231_HBG/ [2] Links: ------ [1] http://phk.freebsd.dk/Leap/20081231/ [2] http://phk.freebsd.dk/Leap/20051231_HBG/
_______________________________________________ LEAPSECS mailing list [email protected] https://pairlist6.pair.net/mailman/listinfo/leapsecs
