Normally dhclient is sent to bg and exit 0 during boot to speed up boot time.
The problem is that it takes up to 8 seconds to obtain an ip address in our
network and so services like nslcd do not have a fully configured network
during startup. It would be great to have an option to force dhclient to be
run if fg, in order to prevent the other services to be started before
network is up.
Not sure it's a good idea. Currently, dchlient runs in foreground until it gets
a lease or times out. If we make it to run in foreground indefinitely, this
would block boot-up process, for example. That can be made an option for people
who know what they're doing, but I'd not dare enable it by default.
Good option would be running it in foreground without marking the interface
up but allowing system to boot, but that requires serious changes to ifupdown,
and I think that's not going to happen before the release.
Sounds like a good option to me. Right now, I can workaround by adding a
script which probes if the interface is up and sleeps otherwise to
if-up.d. I make use of ip addr list to do so. Can you perhaps advice a
better way to check if the interface is running?
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
