[ntp:questions] Trouble Simulating Leap Seconds

Brian Inglis Brian.Inglis at SystematicSw.ab.ca
Thu Apr 2 20:57:25 UTC 2015

To get higher resolution try something like:
	while sleep 0.1 ; do date -u -Ins ; done

Take care. Thanks, Brian Inglis

On 2015-04-02 08:08, Jim Witschey wrote:
> UTC -- I'm using `date -u`.

> On Thu, Apr 2, 2015 at 2:44 AM, Marco Marongiu <brontolinux at gmail.com> wrote:
>> 23:59:59 of which timezone?
>> Il 02/apr/2015 03:14 "Jim Witschey" <jim.witschey at datastax.com> ha scritto:

>>> I'm trying to simulate a leap second on a cluster of Ubuntu AWS
>>> instances via NTP, and I could use some help. I've set up a basic NTP
>>> server with a leapfile as described here:
>>> https://support.ntp.org/bin/view/Dev/LeapSecondTest
>>> The server's warning for the upcoming leap second seems to propogate
>>> to the clients, as I see `leap_armed` in the output for `ntpq -c rl`
>>> before midnight, and `leap_event` afterwards. However, when I loop
>>> `date -u` over the leap second, I don't see a leap second getting
>>> inserted -- I expect 23:59:59 to last for 2 seconds, but it doesn't.
>>> The time goes straight from 23:59:59 to 00:00:00 the next day.
>>> In addition, I don't see any information about inserted leap seconds
>>> in the logs when I search with `dmesg | grep leap` or `sudo grep leap
>>> /var/log/syslog`.
>>> Am I missing something? I can provide more information on request.

More information about the questions mailing list