Interesting. ntp-2.gw.uiuc.edu is an old Cisco box running 12.0(27).
I wasn't around for the leap second, so I don't have any information
about what happened, and its log is completely silent. FWIW, its
clock and NTP process appear fine now. It's synced off our GPS clock,
which may be a
On (2005-12-31 17:18 -0500), Deepak Jain wrote:
Linux seemed to survive happily too
[EMAIL PROTECTED] ~]% dmesg|tail -n1
Clock: inserting leap second 23:59:60 UTC
Curious though that not so many people who've I asked got these messages,
only explanation I can think
Just a reminder, at midnight UTC there's a leap second added to most
time systems.
Some time systems will stop the clock at 23:59:59.99 for 1
second, some will display 23:59:60 for a second.
Since the last leap second (1998), leap second aware time keeping
systems(NTP, GPS, etc)
On Dec 31, 2005, at 11:58 AM, Kevin Day wrote:
Just a reminder, at midnight UTC there's a leap second added to
most time systems.
Some time systems will stop the clock at 23:59:59.99 for 1
second, some will display 23:59:60 for a second.
Since the last leap second (1998), leap
Cisco seems happy as well. (adding leap second, leap second occurs at), etc.
sh ntp status
Clock is synchronized (adding leap second), stratum 2, reference is
xxx.xxx.xxx.xxx
nominal freq is 250. Hz, actual freq is 249.9975 Hz, precision is 2**18
reference time is C7617E39.3A0B3D8C
Last NTP spam:
I'm by no means an NTP expert, if anyone else is, please pipe up.
About 30 minutes before the leap second should have occurred, several
of our systems reported xntpd[13742]: time reset 0.958385 s, which
was really strange. They moved the wrong direction, and they did it
Kevin Day wrote:
Last NTP spam:
I'm by no means an NTP expert, if anyone else is, please pipe up.
About 30 minutes before the leap second should have occurred, several
of our systems reported xntpd[13742]: time reset 0.958385 s, which
was really strange. They moved the wrong direction,
On Sat, Dec 31, 2005 at 05:06:59PM -0800, Roy wrote:
Kevin Day wrote:
Last NTP spam:
I'm by no means an NTP expert, if anyone else is, please pipe up.
About 30 minutes before the leap second should have occurred, several
of our systems reported xntpd[13742]: time reset 0.958385 s,
Peter Lothberg's Post-Soviet-Era cesium clock. :-)
Yes!
Cheers!
- ferg
-- Jared Mauch [EMAIL PROTECTED] wrote:
[snip]
I suggest changing your clock sources to something more reliable
if you're seeing folks that are not diligent stratum-1 sources.
I suggest this as a source:
Once upon a time, Kevin Day [EMAIL PROTECTED] said:
While I can't say anything broke on our network as a result of the
leap second, a good percentage of our gear lost NTP sync or had some
kind of NTP problem around midnight UTC. You may want to check your
NTP status at some point, in
--On December 31, 2005 6:57:45 PM -0600 Kevin Day [EMAIL PROTECTED]
wrote:
While I can't say anything broke on our network as a result of the leap
second, a good percentage of our gear lost NTP sync or had some kind of
NTP problem around midnight UTC. You may want to check your NTP
11 matches
Mail list logo
