Re: [ntp:questions] Failed to test leapsecond's handling

2012-03-12 Thread Martin Burnicki
Hi Marco, Marco Marongiu wrote: Hi Miroslav, all It looks like it took more than 15 seconds for this to work correctly... In my post from the earlier thread I wrote: Then you should set UTC time on that server close to (maybe 1 or 2 hours before) midnight for the correct leap second date,

Re: [ntp:questions] Failed to test leapsecond's handling

2012-03-12 Thread Marco Marongiu
Hi Martin, all On 12/03/12 12:16, Martin Burnicki wrote: In my post from the earlier thread I wrote: Then you should set UTC time on that server close to (maybe 1 or 2 hours before) midnight for the correct leap second date, e.g. 22:00 UTC on June 30, 2012, and start ntpd on the server.

Re: [ntp:questions] Failed to test leapsecond's handling

2012-03-08 Thread Miroslav Lichvar
On Thu, Mar 08, 2012 at 01:10:02PM +0100, Marco Marongiu wrote: But when I graph the time log (see the log target in the makefile), I don't see the leap second kicking in. Based on Mills' The NTP Timescale and Leap Seconds[1], when the leap second kicks in, I'd expect two consecutive date

Re: [ntp:questions] Failed to test leapsecond's handling

2012-03-08 Thread Miroslav Lichvar
On Thu, Mar 08, 2012 at 02:28:07PM +0100, Miroslav Lichvar wrote: In a clknetsim simulation with ntp-4.2.6p5 I can see the clock is correctly stepped by 1.0 second. Here is the ntpd log (in UTC+2 timezone): http://pastebin.com/ZRi6qv8E In another simulation set to start 15 seconds before