https://bugzilla.novell.com/show_bug.cgi?id=218726 ------- Comment #25 from mskibbe@novell.com 2006-11-28 04:33 MST ------- (In reply to comment #24)
(and thus most wont notice problems).
no. there are enough compnies with enough high critacal time depend software. but this doesn't matter. it's important to find the problem but in my opinion i found the problem: your hw clock - i cannot say more thats the cause i closed the bug with _WORKSFORME_ which mean you should find the error and reopen the bug. but let us search the problem together.
For a test I disabled the usage of local clock in NTP and still have the same results.
I started the xntpd by hand using "xntpd -d -D9" (with local clock disabled) and got following (for me this looks as if NTP never gets the NTP packets from the other side, although they arrive). Probably the networking code has some side effects? Maybe getting EINTR is not handled correctly (or at all).
[...] good idea but next time attach the output in an attachment not in the text. i take a look on this output. that do you mean with EINTR? p.s. comment #20 - you see in the output that ntp could reached servers -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.