Subject: Re: dhclient still taking up 95% of CPU
To: Peter Seebach <seebs@plethora.net>
From: Laine Stump <lainestump@rcn.com>
List: current-users
Date: 10/22/2000 13:51:37
Laine Stump <lainestump@rcn.com> writes:

> However, even if select is fixed, timeval is still only valid up to 2
> billion something (since it's a signed long), while a dhcp lease time
> can be up to 4 billion (unsigned long). So dhcp still needs to at
> least make sure that it isn't setting tv_sec to a negative value (as a
> matter of fact, my system would still be broken with a fixed select(),
> because the lease time from RCN is 0xFFFFFF3F seconds)

I should think longer before I speak - dhcp already *is* somehow
limiting/reducing the timeout it uses for select: when I was running
in the debugger, it showed the timeout as 1,175,253,196, in spite of
my much longer lease.