chkconfig xinetd on ; kill -HUP `cat /var/run/xinetd.pid` is one of the few ways to do this.
"chkconfig <daemon> on" basically creates a symlink from /etc/init.d/<daemon> to /etc/rc.d/rc.2/S##<daemon> so when "init" comes through that dir (on boot) it runs all the S## with an argument of start. It turns "on" that daemon. most daemons (or program that runs in the background or detached) write a pid file when they start. kill -HUP <pid #> tells most daemons to re-read their configuration files. Telnet, echo, etc. are part of that configuration file(s) for xinetd. So we just say `cat pid` (which returns the current pid) and send it a -HUP. xinetd re-reads the config, notices telnet, echo, whatever are now enabled, and then starts listening on those ports to service requests. just in case you wanted that over explained :) On Wednesday 22 January 2003 3:16 pm, John Salamone wrote: > The service XINETD is already running but when I start another service I > get the message stated earlier. <snip> -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
