From d0f565c5c0370424ac78a127f31a60396d280b95 Mon Sep 17 00:00:00 2001 From: Albert Cheng Date: Tue, 23 May 2006 10:06:23 -0500 Subject: [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. --- bin/runtest | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/bin/runtest b/bin/runtest index ce55f58..0e7db9e 100755 --- a/bin/runtest +++ b/bin/runtest @@ -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" -- cgit v0.12