Roger Oberholtzer wrote:
On Tue, 2011-07-19 at 11:23 +0200, Joachim Schrod wrote:
Roger Oberholtzer wrote:
After boot (real time was 21.48), I see this is /var/log/messages:
Jul 18 23:48:59 barracuda ntpd[3033]: ntpd 4.2.6p3@1.2290-o Tue Jun 7 03:10:56 UTC 2011 (1)
As Per wrote, at the time of start of ntpd, system time is already set incorrect. You need to investigate that first and stop to fuss about ntpd not synchronizing to its time sources - you can do that later... ;-)
Of course. But my goal here is not so much to simply correct my broken system. I could do that is short order. My exercise is to see why it is wrong with the goal being that I can keep it from happening again (if possible).
I understand this. But to see "why it is wrong" means to find first the root cause of this issue and then decide if that's an isolated issue or one that could happen more often. And by now we can tell with a very high probability that the root cause is not ntpd itself, but either boot.clock or the ntpd start script with any action that happens before ntpd. Thus I posted the proposed actions for analysis if boot.clock runs amok or if one has to look at /etc/init.d/ntpd. Joachim -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Joachim Schrod Email: jschrod@acm.org Roedermark, Germany -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org