On Wed, 2006-07-12 at 08:24 +0200, Kurt Roeckx wrote: > On Wed, Jul 12, 2006 at 12:22:25AM +0100, Sam Morris wrote: > > found 325842 1:4.2.0a+stable-9 > > thanks > > > > This looks like a bug I reported some time ago. I was never able to > > reproduce it reliably so I closed it, but I have seen it crop up > > occasionally since then. > > > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=327138 > > I've tried reproducing this bug by starting 2 ntpd's and things > like that, but was never able to reproduce it. > > You marked this bug as found in 1:4.2.0a+stable-9? What is it > exactly that you found in this version? That you lose peers? > That there where 2 ntpd's running? Can you please explain a > little more?
Both--two ntpd processes are running, but it is not the case that ntpd was started twice. It seems that the daemon never finishes initialising: ntp_initres seems to be part of the initialisation/daemonisation/forking process. For some reason, this process never finishes, and so ntpd never starts communicating with peers. Unfortunately I have never been able to reproduce the bug in a debugger. -- Sam Morris http://robots.org.uk/ PGP key id 5EA01078 3412 EA18 1277 354B 991B C869 B219 7FDB 5EA0 1078 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]