I've adapted and tried the workaround developed by David Harel (the initial bug reporter) but that does not work with interfaces that are beyond NetworkManager's jurisdiction (e.g. vboxnet0).
So we're left with two equally undesirable options - remove any interface binding condition (i.e. poor security). - develop a job polling for any interface status change with the task of systematically restarting smbd. when you bind on vboxnet0, wlan0 and eth0 interface status changes can be a pretty frequent event. So +1 for the wishlist. Why could smbd not simply listen (as in listener design pattern) to net interface changes and bind/unbind on any interface configured in smb.conf an when-available basis ? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/374589 Title: Samba fails to start at boot when not connected to network (and specific interfaces are configured) -- 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
