Fact that ifup runs so early from this udev rule breaks asynchronous mounting of network shares (nfs/cifs). If you add a CIFS share to /etc/fstab, set it to auto, it might not get mounted at boot anyway. It should get mounted as a result of /etc/network/if-up.d/mountnfs script run, during ifup, but... ifup will get run by udev early, and this script will either fail, or won't run as a result of another script failing. Later, when /etc/init.d/networking calls ifup -a, ifup will see that interfaces are already up, and do nothing. As a result, share will remain unmounted. It will of course work if you run the /etc/init.d/networking script by hand (or just ifdown/up). And yet another workaround is to set ASYNCMOUNTNFS=no in /etc/default/rcS. But truth is, those are just workarounds, and the actual problem lies in 85-ifupdown.rules.
What are the cases that it SHOULD and WILL run properly? How about changing that ifup call from "--allow auto" to "--allow udev", and just make sure that interfaces that are safe for such early treatment are marked with such class in /etc/network/interfaces? -- ifupdown-udev integration should be thought-out more thoroghly https://bugs.launchpad.net/bugs/366967 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
