Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!wuarchive!usc!apple!csibtfr!motcsd!hpda!hpcuhb!hpsmtc1!hp-ses!hplabs!hp-sdd!ncr-sd!ncrcae!hubcap!emory!samsung!cs.utexas.edu!rutgers!aramis.rutgers.edu!paul.rutgers.edu!topaz.rutgers.edu!busboys.rutgers.edu!gaynor
From: gaynor@busboys.rutgers.edu (Silver)
Newsgroups: comp.unix.wizards
Subject: Re: ersh does (was: rsh does not pass back return code)
Message-ID: <Dec.6.06.26.10.1989.7426@busboy>
Date: 6 Dec 89 11:26:00 GMT
References: <4741@solo8>
Lines: 9

shaw@paralogics.uucp writes:
> [rsh's return code is simply indicates whether a connection could be
>  established or not?!]

As far as I can tell, you are essentially correct.  Tremendous pain in the ass.
You really have to bend over backwards to get the return value - perhaps put it
on the last line of stdout or stderr, and take it from there locally.

Regards, [Ag]