xinetd delays in in.rshd responses (cluster problem, long)
Les Mikesell
lesmikesell at gmail.com
Tue Nov 8 19:27:44 UTC 2005
On Tue, 2005-11-08 at 12:27, Tim Prendergast wrote:
> There is also no iptables installed, so firewall is out of the equation.
> There should be no DNS involved because every host it talks to in the
> process is in the /etc/hosts file, and the /etc/host.conf is 'order
> hosts,bind'. My /etc/nsswitch.conf has files then dns listed as the args
> after hosts... Technically, this should disable any lookups outside of
> resolving in the hosts file for everything in the hosts file. We all know
> that isn't always the case, which is why I'm asking here on the list. TCP
> wrappers should be minimal, considering I just opened up a ALL:ALL in
> hosts.allow to eliminate that possibility.
If it is practical, strace xinetd through accepting a connection
(with -f to see if your rsh is doing any checks of its own
after the connection is up).
--
Les Mikesell
lesmikesell at gmail.com
More information about the fedora-list
mailing list