Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hi,
anyone know solution about leap second 31st December 23:59:59. and how can we resolve it for RHEL 6.1
please suggest. we find out below url regarding this my be some helpful.
Is there something in the MANY suggestions in the Red Hat document that you linked to, that you don't understand? There are numerous options listed...did you not see this?
Quote:
Originally Posted by RHEL Doc
By default, Linux systems not using NTP or PTP to synchronize their timekeeping will not correct for leap seconds, and the time reported by these systems will have a one-second difference relative to UTC after the leap second correction. You should reset the clock manually after leap seconds occur.
And, since you're using RHEL 6, have you contacted Red Hat support and asked? You are PAYING FOR RHEL, right??? Since you are, your system should be patched and up to date, and you'll have the kernel patches in place to handle such things. You were also given suggestions for time keeping two years ago: http://www.linuxquestions.org/questi...er-4175523776/
After the leap second there will be a fault in timer functions, and certain applications will misbehave.
Setting the time will clear the leap flag and give instant relief
Code:
date -s now
Or reboot.
This is because 6.1 has a bug. Upgrade to 6.2 (with the latest kernel patch) or higher, and the bug is fixed.
Last edited by MadeInGermany; 12-28-2016 at 03:26 AM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
