In message <wkvgul3gbz.fsf@idris.laine.org>, Laine Stump writes:
>seebs@plethora.net (Peter Seebach) writes:
>
>> In message <wkbswe47cb.fsf@idris.laine.org>, Laine Stump writes:
>> >This has been the case on my system ("RealPC", i386) for several
>> >months. Ted did "some stuff" to the code awhile back, but it didn't
>> >help my situation - once it starts up, dhclient gets its lease, then
>> >continues using 95% of CPU until I kill it.
>> 
>> I believe RealPC is the same code, so it's probably their fault.
>
>Are you expanding on my joke, or is there actually a company called
>"RealPC"? I was just referring to the fact that I'm running on actual
>i386 hardware, not on an emulator ;-)

Oh, never mind.  "RealPC" is the name of a product that someone used to sell,
I think it was VirtualPC without Windows.

>Yeah probably. It hasn't been high enough on my personal list of
>things to do, though. Similarly with the new problem I'm seeing with
>dhcpd. I'd hate to see 1.5 released with problems like this, though...

If someone who knows anything about DHCP would be willing to help, I'm
interested in debugging this.  Once my sup is done, I plan to build a
debugging version from source, and start using the naive, obvious, approach;
run it a bit, then start tracing and watch where the loop is.

-s