On Thu, Feb 02, 2006 at 10:05:44PM -0800, John T. Yocum wrote: > I've been having a same sort of issue that others have reported. After > dhclient has been running for a random length of time, it suddenly > starts consuming a large amount of CPU. Unfortunately for me, the > longest it tends to run is 48 hours before acting up. > > I did get it rebuilt with debug symbols, and got a stack trace from it, > while it was acting up. Hopefully, it will be useful.
I really need a core dump. A single stack trace just tells me the packet processing routing isn't working (or at least everything is getting rejected). Unfortunatly, I haven't had any luck finding bugs there by inspection. -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4
pgp6aMMERprXM.pgp
Description: PGP signature