Dear all,

I can't run samba at my Laptop (fedora11 gnome).
I have installed the packages:
samba, samba-client, samba-common, samba-swat, samba-winbind, and system-config-samba. (I have removed + installed again&again&again!)

Then I enabled the winbind server the nmb server and the smbd server:
su -c 'chkconfig --add smb'
su -c 'chkconfig --list 2345 smb on'
I did it for the 3.
I restarted the laptop...
When I try to run the samba I just can't...
System-Administration-Samba don't do nothing
But in terminal I type $system-config-samba and when I enter the root pass
I receive this:
Traceback (most recent call last):
File "/usr/bin/system-config-samba", line 49, in <module>
mainWindow.MainWindow (debug_flag = debug_flag, use_dbus = use_dbus)
File "/usr/share/system-config-samba/mainWindow.py", line 104, in __init__
self.samba_data = sambaConfig.SambaConfig (self.samba_backend)
File "/usr/lib/python2.6/site-packages/scsamba/core/sambaConfig.py", line 29, in __init__
self.parseFile ()
File "/usr/lib/python2.6/site-packages/scsamba/core/sambaConfig.py", line 32, in parseFile
return self.parse (self.backend.readSmbConf ())
File "/usr/lib/python2.6/site-packages/slip/dbus/polkit.py", line 65, in enable_proxy_wrapper
return func (*p, **k)
File "/usr/lib/python2.6/site-packages/scsamba/dbus/proxy/sambaBackend.py", line 48, in readSmbConf
return self.dbus_interface.readSmbConf ()
File "/usr/lib/python2.6/site-packages/dbus/proxies.py", line 140, in __call__
**keywords)
File "/usr/lib/python2.6/site-packages/dbus/connection.py", line 630, in call_blocking
message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Python.Exception: Traceback (most recent call last):
File "/usr/lib/python2.6/site-packages/dbus/service.py", line 702, in _message_cb
retval = candidate_method(self, *args, **keywords)
File "/usr/lib/python2.6/site-packages/slip/dbus/service.py", line 81, in wrapped_method
retval = method (self, *p, **k)
File "/usr/lib/python2.6/site-packages/scsamba/dbus/service/sambaBackend.py", line 52, in readSmbConf
return self.backend.readSmbConf ()
File "/usr/lib/python2.6/site-packages/scsamba/core/sambaBackend.py", line 104, in readSmbConf
self.parser.parse (filecontents)
File "/usr/lib/python2.6/site-packages/scsamba/core/sambaParser.py", line 281, in parse
section = SambaSection (self, token.value)
File "/usr/lib/python2.6/site-packages/scsamba/core/sambaParser.py", line 44, in __init__
if not prototype and not self.set_name (name):
File "/usr/lib/python2.6/site-packages/scsamba/core/sambaParser.py", line 82, in set_name
raise Exception ("section name must be enclosed in brackets")
Exception: section name must be enclosed in brackets


Can anyone help me please????

Does /etc/samba/smb.conf exist?

Try running "testparm" to check smb.conf for errors if it exists.
Double check if the smb (or is it smbd) symlinks exist in /etc/init.d/rc.5/ and rc.3, etc.
Look at the startup script itself in /etc/init.d/. do you see a line like this:
# chkconfig: 2345 20 80

Try restarting the services from the console using the service commaand. Do you see any error messages.

Since you have swat, you could use that to configure samba. run "sudo chkconfig swat on" to enable it in /etc/xinet.d/swat, and point your web browser to "http://localhost:901". From there you can configure samba and restart services.

Your python installation could be corrupt as well (or the wrong version) but the failures seem to deal with a missing smb.conf file. If the other system-config-* modules work, then python should be OK.

Thanks a lot for your reply!!
1) Yes the file exists.
2) I didn't found any /etc/init.d/rc.5/ BUT i found /etc/rc.* etc...
3) Whats is the filename of the start up script?(I am new to linux!)
4) I restarted all the services and I didn't receive any error.
5) OK I enabled swat and I am able to browse samba gui from my browser. BUT SELinux was alerted me with this:
SummarySELinux is preventing the swat from using potentially mislabeled files (/root). Detailed DescriptionSELinux has denied swat access to potentially mislabeled file(s) (/root). This means that SELinux will not allow swat to use these files. It is common for users to edit files in their home directory or tmp directories and then move (mv) them to system directories. The problem is that the files end up with the wrong file context which confined applications are not allowed to access. Allowing AccessIf you want swat to access this files, you need to relabel them using restorecon -v '/root'. You might want to relabel the entire directory using restorecon -R -v '/root'.
6) I don't have problems with other system-config-*, the only problem is samba.


Best Regards,
Antony.

On my system, the startup script is /etc/rc.d/smb.
/etc/rc.d is a symlink to /etc/init.d on SuSE linux.
Your startup script could be smbd instead.
There will also be a /etc/rc.d/nmb and /etc/rc.d/winbind script as well.
There will be links to them in /etc/rc.d/rc.{2..5}/ given the run levels you indicated.

My smb service script starts with this header:
The smb service starts the nmb, winbind and cupsd services entering run levels 3 and 5.

I used to have Fedora 11 on my netbook until recently. I thought that it had a /etc/init.d/ directory.
You could run "rpm -qf /etc/rc.d"
Then validate the package that is returned:
sudo rpm -qV <package_name>

or all in one step:
sudo rpm -qV $(rpm -qf /etc/rc.d)