On Sun, July 8, 2012 9:53 pm, Amos Shapira wrote: > 1. The leap second happened at the end of June, a week ago. He reports > that it started earlier. 2. You don't need to reboot, it's possible to just > re-set the clock, e.g. "/etc/init.d/ntpd stop; date; date `date > +%m%d%H%M%C%y.%S`; date; > /etc/init.d/ntpd start" (from > http://blog.contegix.com/2012/07/01/redhat-leap-second-fix/).
On Sun, July 8, 2012 9:53 pm, Amos Shapira wrote: > 1. The leap second happened at the end of June, a week ago. He reports > that it started earlier. 2. You don't need to reboot, it's possible to just > re-set the clock, e.g. "/etc/init.d/ntpd stop; date; date `date > +%m%d%H%M%C%y.%S`; date; > /etc/init.d/ntpd start" (from > http://blog.contegix.com/2012/07/01/redhat-leap-second-fix/). Amos, Darrin, thanks upon looking closer, the problem appears to have started around 3am on 26/6 as it is, I noticed there was a fairly recent f/w update, so, after uploading I needed to reboot anyhow -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
