Red Hat Bugzilla – Bug 34884
Installing Samba from RPM does not provide service
Last modified: 2007-04-18 12:32:33 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0)
After installing the Samba RPMs, Redhat fails to run silently as either a
Samba server or client.
Reproducible: Didn't try
Steps to Reproduce:
1. Install Redhat 7.0 without Samba support
2. Use GnoRPM to install samba and samba-common RPMs
Actual Results: 3. Samba does not start on reboot
4. The new Samba Configuration icon in Gnome gives a 404 error in any
Expected Results: Documentation on the Web site or in the RPM should
indicate how to proceed with configuring this Samba install.
Additionally, the RPM should have taken care of most of the steps listed
in Additional Information.
The packaging of the Samba RPM breaks a number of things in the standard
documentation for installing Samba, and so a Redhat FAQ is probably
If you fail to install Samba during the original install, and then later
attempt to install it from the RPMs, several highly non-obvious
intermediate steps are required to get Samba to begin to function properly.
1. Install xinetd. (Xinetd should be a dependency of the Samba RPM but
2. Configure xinetd to start at boot time. (Merely installing the xinetd
RPM, for some reason, does not configure /etc/rcX.d correctly.)
3. Install samba and samba-common RPMs.
4. If you intend to use swat for configuration of Samba (and everybody
does), edit /etc/xinetd.d/swat and comment out the "disable = no" flag.
5. Start xinetd: /etc/rc.d/xinetd restart
6. Start samba: /etc/rc.d/smb restart
7. Point a Web browser to http://localhost:901 to configure Samba.
You can set up all of xinetd, samba, & swat to run at boottime with
ntsysv. It's the standard Red Hat way of enabling services.