On Thursday 16 August 2007 16:16, Sloan wrote: > Carlos E. R. wrote: > > The Thursday 2007-08-16 at 11:48 -0700, Sloan wrote: > > >>> rcntpd restart > > >> > > >> Which will not work at all if he is not using ntpd. > > > > > > IIUC the discussion concerned how to best restart ntpd. The OP was > > > concerned about the accuracy of time on his linux system, and ntpd (or > > > periodic ntpdate) is the obvious answer. > > > > No, it isn't. Not if he has a missaligned "/etc/adjtime", as he surely > > has, and that is not solved by restarting ntpd a hundred times. Everytime > > he boots up the time would be bad again. > > I've not seen that condition in 10 years among the few hundred linux > boxes here, but should /etc/adjtime actually be defective, one could > just nuke it and be good to go. I'd be more concerned with the root > cause, i.e. how did /etc/adjtime get corrupted in the first place. >
Hi Joe, that was problem occasionally after some kernel updates that triggered avalanche of complains on shifting clock. I had that 2 times, and above procedure helped every time. If it doesn't help than we can go and figure out what was the root cause. -- Regards, Rajko. -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
