Confirmed on maverick, this is a problem with /etc/init/smbd.conf using
start on local-filesystems
I have not tested this, but one work around may be to change this to
start on started rc
which will cause smbd to come up after all of the traditional init.d
scripts have been started.
For the long term, services which create or change network topologies
will need to be started as a group and then emit a signal that controls
when network-aware services (like nmbd especially) are started.
** Also affects: ifupdown (Ubuntu)
Importance: Undecided
Status: New
--
openvpn is started after samba (smbd, nmbd)
https://bugs.launchpad.net/bugs/613999
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openvpn 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
