There was bogus adapter information in /etc/network/interfaces . I removed that. Consequently, my computer failed to boot as the samba / nmbd script was waiting for a network event which would never happen. The only adapter listed in /etc/network/interfaces was lo, which would not generate the necessary trigger to start samba. Consequently, Init hung on waiting for the eth up event to start smbd and nmbd.
I noticed bridging events in the /etc/init directory, then discovered bridging functions are now 'formalised' in /etc/network/interfaces. I moved my configuration to there, then removed my original script from init. So my bridging now works properly, and via the formal method. Since upstart could now bring my interfaces up, this has solved that problem. So this is not a bug with samba, or the scripts because if the formal route to bridging is adopted, all works well. This has, however, created another problem unrelated to this bug; DHCPd will not start. Apparently, upstart is trying to start DHCPd before the network interfaces are up. But that is OT here. -- nmbd dies on startup when network interfaces are not up yet https://bugs.launchpad.net/bugs/462169 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
