Opened 12 years ago

Closed 11 years ago

Last modified 11 years ago

#57 closed defect (wontfix)

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 eCS (OS/2) 1.0.1
Component: Samba Server Version: 3.0.28a
Keywords: winbind separator Cc:

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 (5)

comment:1 Changed 12 years 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 "\"

comment:2 Changed 11 years ago by ydario

  • Milestone set to Samba Server for OS/2 1.0.1

comment:3 Changed 11 years ago by herwigb

Just found out that this is a cross platform bug.

comment:4 Changed 11 years ago by herwigb

  • Resolution set to wontfix
  • Status changed from new to closed

http://lists.samba.org/archive/samba-technical/2007-April/053097.html http://threebit.net/mail-archive/samba/msg01149.html http://markmail.org/message/ij6te2otzywfegzl

I looked into the official Samba 3.3.3 source code and found no evidence that this is fixed there, so it does not make sense to try to fix it here, as any utility that uses testparm.exe as a syntax checker for smb.conf (such as sscc.exe) will have to deal with that problem.

comment:5 Changed 11 years ago by herwigb

  • Version set to 3.0.28a
Note: See TracTickets for help on using tickets.