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). Since we will be using this time as part of a data timestamp system, I need to know what could mess it up so it does not happen again. Of course, as there are probably a zillion things that could cause this, perhaps I have a loosing battle ahead of me. Yours sincerely, Roger Oberholtzer OPQ Systems / Ramböll RST Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 roger.oberholtzer@ramboll.se ________________________________________ Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden www.rambollrst.se -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org