Samba Setup Double Directories

[Google Code Exporter]

What steps will reproduce the problem?
1.Go To "Services > Network > smb > Configure".
2.Add a new directory in "Directories to export to other hosts" by clicking on 
"Browse".  Any directory will do. Then click on "OK".
3.Click on "Submit".

What is the expected output? What do you see instead?
The new directory should appear in the list.  All the directories that were 
setup before will appear twice in the list.

What version of the product are you using? On what operating system?
RC1 - Windows 7 SP1 - x64

Please provide any additional information below.

Original issue reported on code.google.com by [e-mail] on 20 Oct 2011 at 3:20

[Google Code Exporter]

Can you please attach your /etc/samba/smb.conf file?

Thanks

Original comment by [e-mail] on 24 Oct 2011 at 1:56

[Google Code Exporter]

I started a fresh RC1, with default settings, none saved, and couldn't 
reproduce this issue.
I was only able to reproduce it if I delete the line

#!# add extra shares below, don't change shares above, dont change or remove 
this line

from /etc/samba/smb.conf. Have you deleted it?

That line marks the end of the [Global] and [Printers] sections and the start 
of user area.

Original comment by [e-mail] on 24 Oct 2011 at 3:20

[Google Code Exporter]

I was getting the same issue when trying to map 2 shares to the same folder 
(one read only, the other writeable but non browseable)

Original comment by [e-mail] on 26 Oct 2011 at 8:26

[Google Code Exporter]

Have you used SWAT?
Swat will remove the needed #!# comment, and without it shares will be 
duplicated each time you hit Submit.

I'm closing this issue as I'm now using a different method that does not needs 
the "#!#" special comment.

However, changes made by SWAT to shares will not survive if Alt-F Submit button 
is hit. Global and Printers section options will survive.

Samba supports some 410 options! I can't support 410 options :-o (although I 
admit that only three options for shares is too meager)

Original comment by [e-mail] on 27 Oct 2011 at 3:35

• Changed state: Fixed