Did however see some weird ntp error messages though Jun 30 01:07:05 [192.168.0.1.128.94] 2012:06:30-01:07:05 ntpd[29409]: kernel time sync status change 0011 Jun 30 14:42:25 [192.168.0.1.128.94] 2012:06:30-14:42:25 ntpd[29409]: kernel time sync error 0011 Jun 30 18:10:21 [192.168.0.1.128.94] 2012:06:30-18:10:21 ntpd[29409]: kernel time sync error 0011 Jul 1 01:08:22 [192.168.0.1.128.95] 2012:07:01-01:08:22 ntpd[29409]: kernel time sync status change 0001 On 1 Jul 2012, at 04:31, Colin Johnston wrote:
all seemed to be ok via astaro vm 2012:07:01-00:59:59 VM406 kernel: Clock: inserting leap second 23:59:60 UTC
Colin
On 1 Jul 2012, at 04:23, Jason Hellenthal wrote:
Would have replied to a later message but none looked to be just perfect so Ill reply here.
clock.nyc.he.net LOCAL(0) clock.fmt.he.net LOCAL(0) clock.sjc.he.net LOCAL(0)
All went to a LOCAL(0) refid sometime recently after being in .CDMA. for the longest time.
Maybe this is a small part of it but thought I would share the note.
On Sat, Jun 30, 2012 at 06:53:53PM -0700, Wil Schultz wrote:
Leap second bug. *sigh*
--
- (2^(N-1)) _______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages