On Sun, 1 Jul 2012, Erez Zarum wrote: > You could have just done: > service ntpd stop; date -s "`date`"; service ntpd start > Fixed here without even stopping any jvm. > > On Sun, Jul 1, 2012 at 5:07 PM, Mogens Kjaer <mk at lemo.dk> wrote: > >> On 07/01/2012 03:05 PM, Bob Hoffman wrote: >>> --------------------- Kernel Begin ------------------------ >>> >>> >>> 1 Time(s): Clock: inserting leap second 23:59:60 UTC >>> >>> ---------------------- Kernel End ------------------------- >>> >>> hee hee. >>> >>> gotta love it.... >> >> My oracle database running on CentOS 6 didn't love it :-( >> >> Some java processes were >100% CPU after the leap second was added. >> >> Rebooting... The interesting thing to me is that my c5 systems just kept on ticking but my c6 systems had the load go through the roof and fill the logs with things like the following: Jun 30 19:59:59 casper kernel: Clock: inserting leap second 23:59:60 UTC Jun 30 19:59:59 casper tgtd: work_timer_evt_handler(89) failed to read from timerfd, Resource temporarily unavailable Jun 30 19:59:59 casper tgtd: work_timer_evt_handler(89) failed to read from timerfd, Resource temporarily unavailable Jun 30 19:59:59 casper tgtd: work_timer_evt_handler(89) failed to read from timerfd, Resource temporarily unavailable Regards, -- Tom me at tdiehl.org Spamtrap address me123 at tdiehl.org