[Bug 462169] Re: nmbd dies on startup when network interfaces are not up yet

Nicolas M nicolas0martin at gmail.com
Mon May 17 18:16:47 BST 2010


Right, let me precise a bit more what I’m doing. 
I have a home network with various W$ and Ubuntu PCs + a Mandriva (2007) server. 
This server is used for sharing files, printing, scanning, photo/videos web pages, ssh…
Due to variety of OSes, file sharing between W$ PCs and this server uses SMB (Ubuntu PCs use mostly ssh folders). 

Samba is installed on the server, the Mandriva (and formerly Mandrake)
configuration is very close to what explained in the “Using Samba” book:
Both nmbd and smbd daemons are started at boot time.

Now, with Ubuntu, here is what I get, with standard nmbd and smbd conf files : 
-          At boot time : only smbd started.
-          nmbd must be started manually or samba restarted when network is up to have nmbd + smbd operational. 
-          If only smbd is running, file sharing on the server is *not* working: the server is visible from the PCs, but impossible to enter workgroup or shares (they are not visible).
-          If nmbd (and smbd) started, then SMB/Samba file sharing works at 100%

As I explain, due to Wifi, network will come up only after boot (and after nmbd start). 
Having smbd running without nmbd is useless, at least, in my case. 
I don't understand exactly, why we do not start nmbd, even if no network avail: Other daemons using the network *are* started at boot (e.g., ntpd, sshd, ...) even if no network is available.

-- 
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
Server Team, which is subscribed to samba in ubuntu.



More information about the Ubuntu-server-bugs mailing list