Samba server configuration program chokes on highly-customized/missing smb.conf
I've been messing with the samba server settings on my FC5T3 box and I've
found that if I have a highly-customized or missing smb.conf, the GUI Samba
configuration tool will fail to open (for a highly-customized smb.conf) or
crash upon adding a share (for a non-existant smb.conf).
I think that a more reasonable behavior would be to have it prompt the user
to overwrite, then if the user agrees, copy
over /usr/share/system-config-samba/smb.conf.template to /etc/samba/smb.conf,
and then act normally.
Also, I've found that even a little customization is lost if I make any
changes at all using the configuration tool. Shouldn't the user be prompted
before overwriting his/her hand-made changes?
What do you all think?
--Dane