Comment 4 for bug 823878
Revision history for this message
| Robie Basak (racb) wrote Re: smbd failed to start after system restart | #4 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Vasya,
If you manually change /etc/samba/smb.conf to have smbd bind to a specific interface, you also need to edit /etc/init/smbd.conf to make sure the smbd is started only after that particular interface is up, in the style "start on (local-filesystems and net-device-up IFACE=eth0)" (as described in https:/
Ideally upstart would pick up on this automatically, but we also have to cater for environments where a network might not come up until much later if at all, and local access to smbd over loopback should still be available in that case (see https:/
It is unfortunate that a sysadmin would have to know to do this when adding interfaces/bind interfaces only to smbd, so I'm leaving this bug open in case someone can come up with a way of solving this problem without issues in both cases. I'm setting Importance to Low as this workaround is available and the problem only occurs when the sysadmin changes smb.conf by hand.