-
Title
Is Privilege Manager for Unix affected by the Leap second on 30th June 2015? -
Description
Is Privilege Manager for Unix affected by the Leap second on 30th June 2015? -
Cause
A Leap second is due to be added on 30th June 2015 which results in an invalid time of 23:59:60
See the following link for more information on Leap seconds:
http://en.wikipedia.org/wiki/Leap_second -
Resolution
Privilege Manager gets the time and date from the OS as UTC time (number of seconds since the epoch) using the time() function.
When doing any conversions, the application uses standard C functions, e.g. strftime, gmtime, localtime etc., so Privilege Manager is at the mercy of the OS implementation of ‘time’ (and may inherit any leap second issues to which the OS is also vulnerable).
We have performed some tests running continuous Privilege Manager commands through a time change from June 30, 2015 23:59 to July 1, 2015 00:01 on Redhat Enterprise Linux systems and have not experienced any issues.
In the event that Privilege Manager were to receive an invalid time through the OS, any issues would be isolated to events or requests made exactly when the invalid time was received.