dhclient existing when run early in startup

[Tobias Roth]

On Tue, Feb 21, 2006 at 01:28:18PM -0800, Brooks Davis wrote:

> > Possible improvements:
> > 1) change dhclient to accept a timeout on the commandline
> 
> This would be a useful addon.  Actually, I'd like to see both the option
> to specify a shorter one and the option to keep trying forever since
> that's what's wanted in some scenerios.

I've implemented the two switches -i and -t, that override the variables
from dhclient.conf 'retry' and 'timeout'. The patch can be found here:

http://fsck.ch/dhclient_timeouts.diff

As it looks, the OpenBSD dhclient tries to be consistent with the naming
of the switches with isc-dhclient, as much as it's possible (ie -lf has
been changed to -l). Since -r is alrteady taken in isc-dhcp (release
current lease and exit), I opted for -i to specify the retry interval.

I'd also like to do a switch that tells dhclient to only try once, and
then exit, similar to the -1 of isc-dhclient. I'll look into it later.

What do you mean with "keep trying forever"? As I see it, dhclient
already tries forever, as it never exists. Do short enough timeouts
already cover your scenario?

Thanks, Tobias