[CLUE-Tech] Cracked! Mailog entries; xinetd in RHV7.0

[ian]

The one thing you have to watch with xinetd is some of your higher use
ports that aren't running standalone daemons can get slowed down rather
significantly if you don't configure it right.  Also if you use TCP-wrappers
AND xinetd access restrictions you can run into really strange slowdowns.

ie.  FTP would take way too long to initially connect and many of the clients
would timeout (NOTE: this was on the internal network or through an SSH tunnel.)

Also you can just reload the configurations instead of restarting the xinetd.
In RH 7.0 you can do a "/etc/init.d/xinetd reload"  Not sure what the kill signal
is off the top of my head.

http://www.xinetd.org

ian



On Mon, Mar 26, 2001 at 08:58:37AM -0700, Tim Russell wrote:
> Jim -
> 
>    I was a bit taken aback too, but I actually like xinetd quite a bit!  You
> definitely need to be a little more careful with it though, it's quite a bit
> more powerful than inetd, which can be both good and bad.
> 
>    To disable a service, just go into /etc/xinetd.d, edit the service's
> file, and add a "disable   = yes" line that's the same format as the other
> lines.  Then either do a "/etc/rc.d/init.d/xinetd restart" or a "kill -USR2
> <pid" on the xinetd process id.
> 
>    Among other things, I discovered, happily, that it'll do user-level port
> forwarding to an internal system on a firewall last week.
> 
> Tim
> _______________________________________________
> CLUE-Tech mailing list
> CLUE-Tech at clue.denver.co.us
> http://clue.denver.co.us/mailman/listinfo/clue-tech