[opensuse] Leap second and old suse systems
Turns out that I have some very old suse systems, that might be affected by leap seconds this month? I was wondering if running ntp to sync the local time to external ntp sources, isnt that fixing my time on a daily or regular basis anyways, how can a mere second cause trouble if time is adjusted multiple times ever month or week or day anyways? I have some 9.3 x86-64 and some 11.0 x86 and maybe even some other systems that cannot be advanced. Thanks for hints. Regards. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Fri, Jun 5, 2015 at 11:33 AM, cagsm <cumandgets0mem00f@gmail.com> wrote:
Turns out that I have some very old suse systems, that might be affected by leap seconds this month? I was wondering if running ntp to sync the local time to external ntp sources, isnt that fixing my time on a daily or regular basis anyways, how can a mere second cause trouble if time is adjusted multiple times ever month or week or day anyways?
I have some 9.3 x86-64 and some 11.0 x86 and maybe even some other systems that cannot be advanced.
SUSE recommendation is to disable step mode over leap second. See https://www.suse.com/support/kb/doc.php?id=7016150 for details. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Thank you for your hint. On Fri, Jun 5, 2015 at 10:44 AM, Andrei Borzenkov <arvidjaar@gmail.com> wrote:
SUSE recommendation is to disable step mode over leap second. See https://www.suse.com/support/kb/doc.php?id=7016150 for details.
it was even old named xntp stuff, so I was able to add some xntpd parameter (-x) XNTPD_OPTIONS="-x -u ntp" in /etc/sysconfig/xntp and also checked some documentation at: <http://doc.ntp.org/4.2.0/ntpd.html#cmd> Thanks again. Regards. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/08/2015 05:00 AM, cagsm wrote:
Thank you for your hint.
On Fri, Jun 5, 2015 at 10:44 AM, Andrei Borzenkov <arvidjaar@gmail.com> wrote:
SUSE recommendation is to disable step mode over leap second. See https://www.suse.com/support/kb/doc.php?id=7016150 for details.
it was even old named xntp stuff, so I was able to add some xntpd parameter (-x)
XNTPD_OPTIONS="-x -u ntp"
in /etc/sysconfig/xntp
and also checked some documentation at: <http://doc.ntp.org/4.2.0/ntpd.html#cmd>
Thanks again. Regards.
As an exercise, I put together a small script that should work as a root crontab to monitor the calendar until 6/29 (0600) for older systems that are vulnerable to leap second issues. The script would then set the ntp '-x' slew mode option in /etc/sysconfig/ntp, and restart ntpd. The script then monitors the dates until 7/1 (0600), restores the original config and restarts ntpd resuming normal operations. NOTE: A concern is if sysconfig periodically sweeps /etc/sysconfig running something like 'files' to remove any new or unknown files which would eliminate the original config files. In that case a new backup location for the original ntp sysconfig is needed or simply run the script manually on 6/29 and then again on 7/1. dnh, all, let me know if you find any issues or needed improvements with the script. I have tried to think of as many corner cases as possible, but experience has shown any one person rarely considers them all. Check whether your system is one that needs to be set in slew mode to handle the leap second. If it is, test the script against your config and let me know if it does/doesn't work for you. I have tested on an older 11.0 with correct results. I will attempt to attach the script, but if the filter strips it, I'll re-post inline. -- David C. Rankin, J.D.,P.E.
participants (3)
-
Andrei Borzenkov -
cagsm -
David C. Rankin