xinetd delays in in.rshd responses (cluster problem, long)

[Tim Prendergast]

Yes, it does... here's the rsh file in /etc/xinetd.d

[root@]more /etc/xinetd.d/rsh
# default: on
# description: The rshd server is the server for the rcmd(3) routine and, \
#       consequently, for the rsh(1) program.  The server provides \
#       remote execution facilities with authentication based on \
#       privileged port numbers from trusted hosts.
service shell
{
        disable = no
        socket_type             = stream
        wait                    = no
        user                    = root
        log_on_success          += USERID
        log_on_failure          += USERID
        server                  = /usr/sbin/in.rshd
        cps                     = 1000 5
}

The oddity is that the other system also has the USERID entries. I removed 
them just now to test, restarted xinetd.d, and ran the same 'time rsh 
localhost uname -a' with the same results as before. This would indicate to 
me that the IDENT request is taking nearly no time at all (0.001s difference 
in the times with or without the log lines present).

-Tim
----- Original Message ----- 
From: "Les Mikesell" <lesmikesell at gmail.com>
>
> The server side is probably issuing an IDENT query so it can
> log the name of the owner of the initiating socket, which you
> are probably firewalling or ignoring somewhere in between.
> Does your xinetd entry for rsh mention USERID?  If you don't
> need it, take it out.
>
> -- 
>    Les Mikesell
>     lesmikesell at gmail.com
>