Yep, I'm binding it to eth0, which is not unreasonable. I read Bug #125687 and it seems to be the same thing.
It seems that nmbd can start before DHCP has completed getting an IP and it logs the "no network interfaces found" warning and does nothing else. A possible workaround for me is to hack the samba startup script to loop a few times on a check for eth0, and sleep for a while if it's not there: not much point starting samba if there's no network. -- [gutsy] Wrong startup ordering in /etc/rc3.d https://bugs.launchpad.net/bugs/175934 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
