© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
f33e652
(Get the code!)
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.