Excuse me to enter this thread lately, but something looks weird to me here.
I've just experienced the same issue with Lucid, trying to set up samba server, on a Wifi hooked laptop. With current samba-server package, result after Lucid boots is: - smbd is running - nmbd is not running leading to samba and W$ networking failing. Following the advices given in this thread, I can read, at the beginning of these 2 files: - /etc/init/smbd.conf: start on local-filesystems - /etc/init/nmbd.conf: start on (local-filesystems and net-device-up IFACE!=lo) >From what I understand here, we let smbd start at boot in any case, but nmbd only if a network I/F is up (?) For a Wifi laptop, a network interface will only be up, after a user logs in, and activates Wifi using network-manager applet. During or just after boot, Wifi is off. So I just changed nmbd.conf start statement to look exactly as smbd.conf one (i.e.: start on local-filesystems), and now both smbd *and* nmbd gets started at boot, and samba sharing starts fine as soon as Wifi is up after a user logs in. => So my question here: why having a different startup condition for smbd and nmbd, as both daemons need to be running for samba to operate ? -- nmbd dies on startup when network interfaces are not up yet https://bugs.launchpad.net/bugs/462169 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
