On Sat, 2003-02-01 at 21:57, John Salamone wrote: > Brett, > > When i did that i get a prompt back when i typed it which i assume is OK. I > then typed /etc/xinetd.d/swat and typed head -500 swat i received the > following disable = no. When I go out to sevices and try to stop or start > swat I get must enable xinetd. Now what?
ok. I have never seen that message but I am sure we can get this to work. To make sure you understand what is going on, Inetd or the latest incantation, xinetd is a "super server". It listens to ports on a machine as defined by the files in /etc/xinetd.d and if it gets a connection attempt on one of these ports, it launches the program associated with the port and hands off the connection to the newly started program. This allows the machine to no be chewing up a lot of resources for a bunch of seldem used services and adds an extra layer of security by allowing or disallowing connections via the /etc/hosts.deny and /etc/hosts.allow files. You should not have to worry about them now that is just background for your edification. Of course, xinetd has to be running for these services to be managed by it. I get the feeling that it is not by the message you describe. to check if xinetd or a lot of services that are run as standalone daemons in redhat you can run the command service xinetd status eg: [root@bretsony root]# service xinetd status xinetd (pid 3952) is running... if it is not running you can start it with service xinetd start all this is on a running system. The services that can be controlled this way have init scripts in /etc/init.d If you want to start a service at boot or runlevel change, you can use chkconfig xinetd on. ( in all the above examples you can change xinetd for the service under consideration). also chkconfig --list will spit out a list of all services that it knows about and the runlevels that the services will be started. I usually pipe the output into less because it more that fills the screen chkconfig --list |less xinetd services are a little different since chkconfig actually restarts xinetd and essentially starts the service. these are listed at the bottom of the chkconfig --list output so all this is a long winded way of saying look to see if xinetd is running and if not start it as mentioned above. HTH Bret -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
