On Wed, 15 Dec 2004 08:56:45 -0800, Wayne Watson wrote: > > # service xinetd start > > Starting xinetd: [ OK ] > Same. > > > # chkconfig swat on > > # netstat -tpan | grep 901 > > tcp 0 0 0.0.0.0:901 0.0.0.0:* LISTEN 3914/xinetd > No output. No 901 in output. Huh? So not even the xinetd superserver listens on port 901. Now please don't tell me you edited the /etc/xinet.d/swat file manually and in Microsoft Windows or so. In case you did -- what I suspect -- run dos2unix on the file. > > # telnet 127.0.0.1 swat > telnet: swat: bad port That looks broken, too. Does the following work for you at least? $ getent services swat swat 901/tcp I mean, trying to connect with telnet to port 901 doesn't make sense anyway because nothing listens on that port. It's just a basic test. "telnet 127.0.0.1 901" would be the same. > > # /usr/sbin/swat -V > No output. I had to Ctrl-C to break from its grip. Expected result. Old SWAT didn't have that option. Want to test that. > > # /usr/sbin/swat < /dev/null > > HTTP/1.0 401 Authorization Required > > WWW-Authenticate: Basic realm="SWAT" > > Connection: close > > Content-Type: text/html > > > > <HTML><HEAD><TITLE>401 Authorization Required</TITLE></HEAD><BODY><H1>401 Authorization Required</H1>You must be authenticated to use this service<p></BODY></HTML> > > > Got exactly what you show. So /usr/sbin/swat works. It's just not executed by the xinetd superserver. More debugging is necessary there. See above. -- Fedora Core release 3 (Heidelberg) - Linux 2.6.9-1.681_FC3 loadavg: 1.00 1.14 1.33 -- Shrike-list mailing list Shrike-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/shrike-list
