When you define a custo smb.conf, the testparm_command silently ignores that file since the parameters are passed wrong, so compile time default will be used. How-To-Repeat: Define 'samba_server_config="/usr/local/etc/smb_instance1.conf"' in /etc/rc.conf and intentionally include a mistake in custom conf file before starting samba. Samba will start even testparm fisrt should look for mistakes, but it doesn't check the same config file that will be used by the daemons (that part is perfectly working in samba_server.in).
Responsible Changed From-To: freebsd-ports-bugs->timur Over to maintainer (via the GNATS Auto Assign Tool)
A commit references this bug: Author: timur Date: Mon Jun 23 18:47:51 UTC 2014 New revision: 358993 URL: http://svnweb.freebsd.org/changeset/ports/358993 Log: Security update for Samba 3.6, 4.0 and 4.1. PR: 190166 Security: CVE-2014-0244 CVE-2014-3493 CVE-2014-0239 CVE-2014-0178 Changes: head/net/samba36/Makefile head/net/samba36/distinfo head/net/samba4/Makefile head/net/samba4/distinfo head/net/samba4/files/patch-buildtools__wafadmin__Tools__config_c.py head/net/samba4/files/samba_server.in head/net/samba41/Makefile head/net/samba41/distinfo head/net/samba41/files/patch-buildtools__wafadmin__Tools__config_c.py head/net/samba41/files/samba_server.in
I originally sent this as gnats (via send-pr). Wondered why my local patch didn't apply to 4.1.9… Thanks for commiting! Do I have to care about the gnats PR? Thanks, -Harry