Bug 8007 - nmbd/smbd don't start without smb.conf
Summary: nmbd/smbd don't start without smb.conf
Status: NEW
Alias: None
Product: Samba 3.5
Classification: Unclassified
Component: Config Files (show other bugs)
Version: 3.5.8
Hardware: All All
: P5 normal
Target Milestone: ---
Assignee: Michael Adam
QA Contact: Samba QA Contact
Depends on:
Reported: 2011-03-11 04:52 UTC by Debian samba package maintainers (PUBLIC MAILING LIST)
Modified: 2013-10-22 20:34 UTC (History)
2 users (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Debian samba package maintainers (PUBLIC MAILING LIST) 2011-03-11 04:52:47 UTC
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?
Comment 1 Michael Adam 2011-03-15 16:56:56 UTC
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.
Comment 2 Volker Lendecke 2011-03-15 17:03:06 UTC
I'd vote for treating a missing one like an empty one.
Comment 3 Luk Claes (dead mail address) 2011-03-15 17:57:04 UTC
I would also opt for treating it as an empty smb.conf.
Comment 4 Debian samba package maintainers (PUBLIC MAILING LIST) 2012-05-08 15:09:13 UTC
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
Comment 5 Jelmer Vernooij 2013-10-22 20:34:22 UTC
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.