On 2011-12-07, Marco Marongiu <[email protected]> wrote: > I had a case at $PREVIOUS_EMPLOYER where we had to do exactly that, or > more precisely: stop ntpd, run ntpdate, then start ntpd again.
You could run "ntpd -gq" instead of ntpdate. > We had a few faulty servers that, for some reason, kept setting the > clock one or two hours backwards, depending if we had DST or not[*]. > Something was happening in the line that the system rebooted/started > with proper time and timezone, then read the UTC time from the hardware > clock as it was local time, and set it on the system. When ntpd started, > it aborted since the machine appeared way off than the tolerated amount. Starting ntpd with "-g" avoids this problem. -- Steve Kostecke <[email protected]> NTP Public Services Project - http://support.ntp.org/ _______________________________________________ questions mailing list [email protected] http://lists.ntp.org/listinfo/questions
