The leap second is a scheduled one second adjustment to the system clock to ensure that system time remains synchronized with the sun. This is done by either adding an extra 23:59:60 second to the clock or skipping the 23:59:60 second on the selected day. Leap seconds do not occur on a strict schedule but are scheduled by the International Earth Rotation and Reference Systems Service (IERS) based on changes to the Earth's rotation.
The next leap second it scheduled for June 30, 2015 23:59:60
With the exception of a minor issue in displaying log events that occurs during the leap second (KB TECH90410) there are no known issues with the operation of Messaging Gateway (SMG and SMG-SP) products resulting from the insertion of a leap second. In most cases, internal date/time tracking is based on the epoch time rather than a date string generated by the operating system. Additionally, there were no reported issues with the Messaging Gateway following the insertion of the last leap second at the end of 2012.
Systems using NTP time synchronization should automatically account for the leap second correction but customers who are concerned regarding interactions between the leap second and Messaging Gateway may disable NTP time synchronization prior to 6/30/2015 23:59:59 and re-enable time synchronization following the addition of the leap second to the time source.
Symantec recommends that where possible Messaging Gateway systems use NTP time synchronization.
This is machine translated content
Login to Subscribe
Please login to set up your subscription.
Didn't find the article you were looking for? Try these resources.