Thomas Schoepf <schoepf@...> writes:
> 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.

What about running it in debugging mode & posting the outputs?

I know of quite a bunch of race conditions and minor bugs in the
dnrd-sources, so it would be helpful if you could be a little bit more
specific.


--
SIGSTOP