Comment 4 for bug 1196975
Revision history for this message
| Clint Byrum (clint-fewbar) wrote Re: [Bug 1196975] Re: ifupdown calling dhclient with -1 causes it to fail when dhcp server unavailable | #4 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
e3ace39
(Get the code!)
Excerpts from Sven Mueller's message of 2013-07-02 15:43:57 UTC:
> Well, that would cover the first failure mode I described, but we experience the second one.
> I don't see any workaround, apart from removing the -1 from the dhclient options.
>
> I'm sorry, but this means that a _part_ of my report might be invalid
> (though we think we saw that issue), but the other part is valid, unless
> you can provide instructions how to not experience this issue.
>
> When an interface is set to use dhcp and is set to an online state,
> dhclient shouldn't give up retrying to renew a lease, but it does.
>
I have to agree with you that dhclient should not give up trying to renew
a lease that is still valid, or trying to obtain a new one once its lease
has expired. Basically if the interface is up and configured for DHCP,
I want it to never give up trying to obtain an interface.
It seems like we're abusing -1 instead of adding a more appropriate
"try forever and stay in the foreground" mode which is I think what we
actually want from -1.