We got a bug report in Debian (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=616075), where it was noticed that nmbd doesn't start if there is no smb.conf file.
Using an *empty* file is OK (of course all default settings are used). Still, isn't there a solution for samba daemons to accept being launched if there's no smb.conf?
Hmmm, several possible solutions:
* keep it like it is. absence of smb.conf is an error...
* treat missing smb.conf like an empty one
* fall back to registry configuration (suggested by jra)
Thinking about what the proper behaviour would be.
I'd vote for treating a missing one like an empty one.
I would also opt for treating it as an empty smb.conf.
Ping? Michael seemed to be waiting for input...and there has been input, voting for treating a missing smb.conf as an empty one. Michael, any chance you can provide a fix for this?
Christian, logged with the common hat of Debian package maintainers
Treating the smb.conf as an empty one (or falling back to the registry backend) if it couldn't be found makes sense, but /only/ if the user didn't specify a path and we were trying to read the default path baked into nmbd.
Running "nmbd -s /home/jelmer/smb.conf" should error out if it can't read that file for some reason.