With Samba 4.15.3, "smbd -b" fails if a file can't be opened at the CONFIGFILE path. With 4.14.11 and prior this worked just fine, hence why I've raised this as a regression (should be low priority though). Workaround is to pass "smbd -b -s /dev/null", but that doesn't allow for discovery of the actual CONFIGFILE build path (it shows /dev/null).
I bisected this regression down to: commit d8f84205337a8baae7f4057a042e74b3d1c3633a Author: Andreas Schneider <asn@samba.org> Date: Tue Jan 5 14:35:39 2021 +0100 s3:smbd: Migrate smbd to new cmdline option parser Signed-off-by: Andreas Schneider <asn@samba.org> Reviewed-by: Andrew Bartlett <abartlet@samba.org> @Andreas: would you mind picking up this ticket?
Created attachment 17083 [details] patch for master Dave, could you please test if this works for you?
Comment on attachment 17083 [details] patch for master I think that's fine, can you create a merge request, so that we can get this into 4.15.4 (in 2 days)?
This bug was referenced in samba master: 6a463c40d755b75b02884f123c19cc2c2845d729
Created attachment 17097 [details] Patch for v4-15-test
Jule, please apply the patch to 4.15. Thanks!
Pushed to autobuild-v4-15-test.
This bug was referenced in samba v4-15-test: 6d158512e8d5a98870016b169fe2f6fb69513808
Closing out bug report. Thanks!
This bug was referenced in samba v4-15-stable (Release samba-4.15.4): 6d158512e8d5a98870016b169fe2f6fb69513808