Operating System - Linux
1832916 Members
2790 Online
110048 Solutions
New Discussion

Re: Samba 3 on RH9 -SWAT config

 
Deeble Tonkin
Regular Advisor

Samba 3 on RH9 -SWAT config

Hi
Anyone got any advice on this. I read the Samba docs but RH9 is a bit different, xinetd instead of inetd. Error message I get is either 'the page contains no data' or a message saying I don't have permisions.
Thanks Deeble.
2 REPLIES 2
Steven E. Protter
Exalted Contributor

Re: Samba 3 on RH9 -SWAT config

Hi deeble,

xinetd works exactly like inetd on Unix and works the same way.

If you make changes to xinetd you run

service xinetd restart

and those changes are implemented.

I can probably help you with this if you post an exact error message.

My thoughts to this point is the swat server doesn't have permissions to use the port its trying to use. Check /etc/services

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Stuart Browne
Honored Contributor

Re: Samba 3 on RH9 -SWAT config

The differences between the way you configure xinetd as against inetd are the confusing part.

For swat, you need someting similar to this in '/etc/xinetd.d/swat':

# default: off
# description: SWAT is the Samba Web Admin Tool. Use swat \
# to configure your Samba server. To use SWAT, \
# connect to port 901 with your favorite web browser.
service swat
{
port = 901
socket_type = stream
wait = no
only_from = 127.0.0.1
user = root
server = /usr/sbin/swat
log_on_failure += USERID
disable = yes
}

By default, this is turned off (disable = yes), and restricted access so only the localhost can use it (only_from = 127.0.0.1).

You will probably need to comment out that line if you want to access it from other machines.

You may also need to update the 'server' line to point to your swat binary (this is taken from a Fedora box).

Also, to have some level of security, you'll also want to firewall it out.

Add this file, update the entries, start it (chkconfig swat on), and look at your log files (/var/log/messages in particular) for errors. Then try to access it.

Other than that, give us more details.
One long-haired git at your service...