On Sun, 11 Mar 2001, Bob Hartung spewed into the bitstream:
BH>Chuck,
BH> That did it: the "disable" part was wrong. One last question then on with
BH>the learning. In order to enable other address to configure swat, are the ip
BH>addresses comma delimited or can I just use 192.168.14.0/24 and get to it
BH>from anywhere on the home network?
I hate to do it but... "man 5 xinetd.conf" will answer that question
better than I can... :-)
BH>Thanks again,
You're welcome!
BH>Bob
BH>Chuck Mead wrote:
BH>
BH>> On Sun, 11 Mar 2001, Bob Hartung spewed into the bitstream:
BH>>
BH>> BH>Response:
BH>> BH> As noted xinetd was updated. It seems that swat does not want to
BH>> BH>start. ps ax | grep swat lists nothing. If in go into linuxconf and
BH>> BH>open the control panel swat is listed but when I check automatic start
BH>> BH>up and then activate changes - linuxconf reports "nothing to do" and it
BH>> BH>does not retain any of the changes e.g. run levels to start up etc. And
BH>> BH>yes, I am logged in as root.
BH>> BH>
BH>> BH>More ideas?
BH>>
BH>> What does your /etc/xinetd.d/swat file say?
BH>>
BH>> Make sure that it says "disable = no" and that the access restriction,
BH>> "only_from = localhost" includes any place else you want to access swat
BH>> from. Then "/etc/rc.d/init.d/xinetd restart". I'll prolly start a flame
BH>> war with this comment but if it was my box I would:
BH>>
BH>> rpm -e linuxconf linuxconf-devel
BH>>
BH>> but I don't care (Flamers hush up... it's my opinion! I've got a right
BH>> to it and you're not going to change my mind!). More damn trouble than
BH>> it's worth IMHO.
BH>>
BH>> Anyway, I hth! :-)
--
Chuck Mead, csm -AT- moongroup.com, Owner, MoonGroup.com
(Note: html formatted email sent to me is filtered & deleted unread)
GnuPG Public Key Available: http://wwwkeys.us.pgp.net
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
