Custom Query (292 matches)

testparm.exe can be used to create a syntactically correct smb.conf by redirecting the output into a file, either with changed value only, or with complete settings (using -v switch).

However, it fails to write proper log level into the file, because no matter what log level is set in the original file, the value in the new file is either 2 (using -v switch) or not set (as 2 is default).

I noticed when trying to implement log level setting in smbmon.exe. The bug is obviously older because I remeber seeing a "vanishing" log level setting with sscc.exe (which uses a similar technique to make sure smb.conf is syntactically correct).

With Samba 3.3.x, when changing smb.conf using SSCC.EXE, smb.conf is trashed when quiting SSCC.EXE.

This is a spin-off from Ticket #145 (as this deals with several unrelated issues).

Reproduction scenario:

1.) Remove any winbind separator line from your smb.conf.

2.) Create a complete smb.conf somewhere by using testparm -v >smb.conf
Now your smb.conf will have a line

winbind separator = \

in your new smb.conf which is the default and perfectly valid. Copy this newly created smb.conf over the one you used before.

3.) Now run testparm -v >smb_broken.conf on that smb.conf again: It will choke and find the following error:

ERROR: the 'winbind separator' parameter must be a single character.

In smb_broken.conf you will find the following line, which is invalid:

winbind separator = 	winbind cache time = 300

Current workaround: Don't use the default winbind separator, use | instead.

Nasty side effect: This breaks every program that uses testparm.exe as a syntax checker in verbose mode for smb.conf