Ticket #57 (new defect)

Opened 6 months ago

Last modified 8 weeks ago

testparm.exe -v produces an invalid smb.conf if the winbind separator character is the default "\"

Reported by: herwigb Owned by: psmedley
Priority: major Milestone: Samba Server for OS/2 1.0.1
Component: Server Version:
Keywords: winbind separator Cc:
Blocking: Blocked By:

Description

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

Change History

Changed 6 months ago by herwigb

  • summary changed from testparm.exe produces an invalid smb.conf if the winbind separator character is the default "\" to testparm.exe -v produces an invalid smb.conf if the winbind separator character is the default "\"

Changed 8 weeks ago by ydario

  • milestone set to Samba Server for OS/2 1.0.1
Note: See TracTickets for help on using tickets.