seebs@plethora.net (Peter Seebach) writes:

> I have a system (VirtualPC) where dhclient is chewing CPU time like mad.  I
> can't find a way to make it log any debugging messages.  Anyone know how much
> CPU time it should be consuming?  It looks to be pretty much busy-looping.

Finally, someone else who has the same problem!!

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.

> The "seconds until lease expires" seems to typically be somewhere in 2017 or
> so, it looks like a random number.

Are you sure it's random, or is the server giving you a very long
lease time (the lease times I get from RCN's cable service really are
in the 20 year range).

> 
> (Oh, and while I'm at it, yes, -current still fails to sleep my "real" i386
> correctly.)
> 
> -s