[svn-r12366] Purpose:

fix.

Description:
More machines stop supporting "rsh machine command".
Worse yet, it hangs the "rsh machine command" process.

Solution:
Switch the order of testing remote execution to use
ssh first, then rsh.

Platforms tested:
no h5committest since it does not test this command.
Change is trivial and will monitor Daily test tonight.
This commit is contained in:
Albert Cheng 2006-05-23 10:06:23 -05:00
parent daa4f9af6c
commit d0f565c5c0

View File

@ -156,7 +156,7 @@ PRINT_TRAILER()
}
# Figure out which remote command to use to reach a host.
# Try rsh first, then ssh.
# Try ssh first, then rsh since fewer machines support rsh exec.
# $1--hostname to reach.
CHECK_RSH()
{
@ -185,10 +185,10 @@ CHECK_RSH()
# Try remote command with host if it responds to ping.
# Still try it if we don't know how to do ping.
if [ no_ping = "$PING" ] || $PING $host $PINGCOUNT >/dev/null 2>&1; then
if rsh $host -n hostname >/dev/null 2>&1; then
RSH=rsh
elif ssh $host -n hostname >/dev/null 2>&1; then
if ssh $host -n hostname >/dev/null 2>&1; then
RSH=ssh
elif rsh $host -n hostname >/dev/null 2>&1; then
RSH=rsh
else
PRINT cannot remote command with $host
RSH="NoRemoteCommand"