I have never observed this behavior.

I would suggest compiling dnrd with debugging (-g) turned on, and the
next time it happens attach gdb to it (gdb dnrd <pid>) and then get a
backtrace on all threads (thread apply all bt)


On Fri, 24 Nov 2000, Thomas Schoepf wrote:

> Do you have any idea what could be done about this?
>
> ----- Forwarded message from Frederic Briere <fbriere@...> -----
>
> Subject: Bug#77793: dnrd: sits in infinite loop
> Reply-To: Frederic Briere <fbriere@...>, 77793@...
> From: Frederic Briere <fbriere@...>
> To: submit@...
> Date: Thu, 23 Nov 2000 02:22:56 -0500 (EST)
>
> Package: dnrd
> Version: 2.7-1
> Severity: important
>
> At least once a day, dnrd will eat up all available CPU cycles, and refuse
> to resolve anything. "/etc/init.d/dnrd stop" says that dnrd is not
> currently running. Killing it by hand and restarting it with
> "/etc/init.d/dnrd start" solves the problem for a few hours.
>
> So far, I have been unable to find a clue as to what causes this
> behavior, and I have noticed no discernable pattern on these failures.
>
>
> -- System Information
> Debian Release: 2.2
> Kernel Version: Linux mysidia 2.2.17 #5 Fri Nov 3 02:56:06 EST 2000 i486
unknown
>
> Versions of the packages dnrd depends on:
> ii libc6 2.1.3-10 GNU C Library: Shared libraries and Timezone
>
>
>
> ----- End forwarded message -----
>
> Thanks
>
> Thomas
> --
> 1024D/B0FA4F49: FA38 2D7E 408F 61E4 BF49 B48F 04BD F5BE B0FA 4F49
> 2048g/C631AF6E: B89D 7BF4 AA6B 569B D9D1 4BF6 3459 66AB C631 AF6E
>
>
>
>

Brad Garcia