Miroslav Lichvar 770db1fe02 sys_linux: always call TMX_SetLeap() in set_leap() ...

The optimization avoiding unnecessary setting of the kernel leap status
can cause a problem when something outside chronyd sets the status to
the new expected value. There will be no TMX_SetLeap() call which would
update the saved status and the kernel status will be overwritten with
the old (incorrect) value in a later TMX_*() call.

Always call TMX_SetLeap() to save the new value and for the log message
selection just check if a leap second has been applied.

2015-08-27 13:26:12 +02:00

13 KiB

Raw Blame History

View Raw