Computing.Net > Forums > Linux > SWAT on SUSE 10.1

Computer Problems? Computing.Net has over 1,000,000 posts about all things technology related! Over 90% answered within 24 hours! Click here to start participating now! Also, be sure to check out the New User Guide.

SWAT on SUSE 10.1

Reply to Message Icon

Name: MikeAtVillage
Date: April 5, 2006 at 04:36:30 Pacific
OS: suse 10.1
CPU/Ram: 666Mhz 512Mb
Product: Tempus
Comment:

Hi,

How can I get Swat running on my Suse 10.1 system. It's there but desn't seem to be running and I can't access in on http://localhost:901

Samba is running OK.

Thanks



Sponsored Link
Ads by Google

Response Number 1
Name: 3Dave
Date: April 5, 2006 at 04:55:53 Pacific
Reply:

Swat is run from inetd. You need to edit /etc/inetd.conf and /etc/services. Check that there is a line like:
swat 901/tcp
in /etc/services and add (or uncomment) a line in /etc/inetd.conf like:
swat stream tcp nowait.400 root /usr/sbin/swat swat
Restart your inetd daemon with:
# kill -1 inetd.pid

(NB You may be using xinetd as opposed to inetd)


0

Response Number 2
Name: MikeAtVillage
Date: April 5, 2006 at 05:49:01 Pacific
Reply:

thanks 3Dave,

It was xinetd.conf and I had already uncommented the swat line in etc/services

Still won't allow me access though. Looking at xinetd.conf it contained nothing else but on a different system the inetd.conf has many lines ?

Mike


0

Response Number 3
Name: 3Dave
Date: April 5, 2006 at 06:19:25 Pacific
Reply:

Is xinetd actually running as it may not be enabled by default?
$ ps -aux | grep inetd

Post up your xinetd.conf.

Have you tried pointing your browser at http://127.0.0.1:901 or your local IP, eg http://192.168.0.10:901 rather than using localhost? You may need to edit any hosts.allow and hosts.deny files.

Are you able to use yast to control services?

Have you tried using webmin? It does so much more than just configure samba via a browser and well worth a look. It does intergrate with swat too which may help.
http://www.webmin.com/


0

Response Number 4
Name: MikeAtVillage
Date: April 5, 2006 at 07:25:39 Pacific
Reply:

Thanks again 3Dave.

Results of ps and xinetd.conf listed below.

I find the yast control rather confusing as each time I go to look "services" is says they are disabled - click on enable, OK, close, open again... disabled. but looking at the "greyed out" list of services shows swat as running. I'm used to swat rather than webadmin - and as you can see I'm struggling enough trying to get to grips with Suse :-))

>>>>>>

ps aux ( my version doesn't seem to like the hyphen -aux ) for inetd and xinetd >

mike 9321 0.0 0.1 2724 672 pts/0 R+ 03:17 0:00 grep xinetd

mike 9301 0.0 0.1 2724 668 pts/0 R+ 03:16 0:00 grep inet

and my entire xinetd.conf >

#
# xinetd.conf
#
# Copyright (c) 1998-2001 SuSE GmbH Nuernberg, Germany.
# Copyright (c) 2002 SuSE Linux AG, Nuernberg, Germany.
#

defaults
{
log_type = FILE /var/log/xinetd.log
log_on_success = HOST EXIT DURATION
log_on_failure = HOST ATTEMPT
# only_from = localhost
instances = 30
cps = 50 10

#
# The specification of an interface is interesting, if we are on a firewall.
# For example, if you only want to provide services from an internal
# network interface, you may specify your internal interfaces IP-Address.
#
# interface = 127.0.0.1

}

swat stream tcp nowait.400 root /usr/sbin/swat swat

includedir /etc/xinetd.d


0

Response Number 5
Name: 3Dave
Date: April 5, 2006 at 08:27:10 Pacific
Reply:

From the outputs of ps it doesn't look as though the xinetd daemon is running as the only thing being returned is the grep command. It should return two lines, one for the search with grep in it but also the actual running service, something like:
root 97 0.0 0.0 1376 72 ? Ss 2005 0:03 /usr/sbin/inetd

Try starting it by hand with:
# /etc/init.d/xinetd start

You should be able to see port 901 open with:
# nmap 127.0.0.1


(PS Just a search for inet would have done as it would have matched both inetd and xinetd)


0

Related Posts

See More



Response Number 6
Name: MikeAtVillage
Date: April 6, 2006 at 01:51:07 Pacific
Reply:

Thanks again 3Dave,

starting by hand failed - so I removed the swat line I'd previously put in xinetd.conf and it then started OK. I have now found /etc/xinetd.d/swat !

port 901 is still not opening.

it would also appear that nmap does not exist on the system :-(

No worries though, I'm giving up on this distro and going back to Mandrake/Mandriva as they seemed to work "straight out of the box"

Thanks again.


0

Response Number 7
Name: reussystem
Date: May 31, 2006 at 11:28:38 Pacific
Reply:

I have the same problem and i resolve it. How I resolve?

Look the file /etc/xinetd.d/swat
and look if you have disable = yes, if yes, change disable = no, then restart with this command: rcxinetd restart

And the problem is resolve.


0

Sponsored Link
Ads by Google
Reply to Message Icon






Post Locked

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.


Go to Linux Forum Home


Sponsored links

Ads by Google


Results for: SWAT on SUSE 10.1

SB Audigy on SuSE 10.1 www.computing.net/answers/linux/sb-audigy-on-suse-101/29099.html

dsl on suse 10.1 www.computing.net/answers/linux/dsl-on-suse-101/29397.html

Suse 10.1 goes black on boot www.computing.net/answers/linux/suse-101-goes-black-on-boot/29145.html