Public bug reported:
Binary package hint: ifupdown
udev brings network connections up when it sees the device appear,
using /etc/udev/rules.d/85-ifupdown.rules
There is no way to stop it bringing them up, and it brings them up in
the background. This means that if you're using autofs with ldap
maps, and using dhcp on a network with Spanning Tree Protocols,
so there's a 30 second delay for the port to come up, and a delay for
dhcp to kick in, most of the init scripts will start before the network
comes up. In this case, autofs starts before the network is up, so it
can't read the ldap entries for automount, and you get no automounter.
The workarounds I'm using at the moment include nuking
/etc/udev/rules.d/85-ifupdown.rules,
or adding a script to restart autofs in /etc/network/if-up.d/.
A better change might be to change /etc/udev/rules.d/85-ifupdown.rules
from
ACTION=="add", RUN+="/sbin/start-stop-daemon --start --background --pid
file /var/run/network/bogus --startas /sbin/ifup -- --allow auto $env{INTERFACE}
"
to
ACTION=="add", RUN+="/sbin/start-stop-daemon --start --background --pid
file /var/run/network/bogus --startas /sbin/ifup -- --allow udev $env{INTERFACE}
"
but I don't know how classes work in /etc/network/interfaces
** Affects: ifupdown (Ubuntu)
Importance: Undecided
Status: Unconfirmed
--
udev brings network connections up in the background
https://launchpad.net/bugs/77325
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
