I too would like to see a solution to this bug.
I think a good solution might be to extend NetworkManager so that it can
be configured to block until it has brought certain interfaces on-line.
So, if you were serving DHCP on eth0 and eth2, you could somehow tell
NetworkManager (probably just a
** Changed in: dhcp3 (Ubuntu)
Status: New = Triaged
** Changed in: dhcp3 (Ubuntu)
Importance: Undecided = Low
--
dhcp3-server is launched before NetworkManager and thus doesn't find interfaces
https://bugs.launchpad.net/bugs/392826
You received this bug notification because you are a
Jacob,
NM what I said about the assignment operator. Seems that is not true
for the Bourne shell in the expression for a test or conditional clause.
Also not true for dash (the sh replacement used in some systems), or
even in other shells set for POSIX compliance. It is also true that the
==
Jacob,
Like I said, the script works for me but on review it looks to be
flawed. I could not find an email addr for you or we could have
reviewed this privately. That might be especially good since I've not
done any scripting for many years. If you would be so kind as to review
the attached
Jacob,
Thanks for that script. It seems to have solved this problem for me as
well. I needed the DHCP server to be usable in a headless server where
no one is there to log in and use some of the other workarounds people
used.
Like others, I wish we did not have to do it this way and still
Thanks, I'll try this script. Moving the dhcp3-server init-script to S99...
doesn't help in my case, btw.
I need the DHCP server to listen on my WLAN card and apparently the delay that
results from moving its launch from S40 to S90 isn't sufficient.
Maybe some kind of feedback from
