From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from groucho.cs.psu.edu ([130.203.2.10]) by hawkwind.utcs.toronto.edu with SMTP id <2724>; Wed, 1 Jul 1992 17:00:37 -0400
Received: from localhost by groucho.cs.psu.edu with SMTP id <2538>; Wed, 1 Jul 1992 17:00:00 -0400
To:	rsalz@osf.org
cc:	rc@hawkwind.utcs.toronto.edu
Subject: Re: rc and rsh 
In-reply-to: Your message of "Wed, 01 Jul 92 15:13:11 EDT."
             <9207011913.AA00693@earth.osf.org> 
Date:	Wed, 1 Jul 1992 16:59:30 -0400
From:	Scott Schwartz <schwartz@groucho.cs.psu.edu>
Message-Id: <92Jul1.170000edt.2538@groucho.cs.psu.edu>


| I don't think I understand the problems people are having with rsh and rc.
| Does this function do the 'right thing' ?
| fn rsh host1 host2... { flag= host=$0 {
|     ~ $1 -n && { shift ; flag=-n }
|     ~ $0 rsh && { host=$1 ; shift }
|     eval 'rsh $flag $host rc -lc ''' ^ $* ^ ''''
| } }

One (general) problem is that rsh leaves open file descriptors hanging
around in its child processes.  The solution I posted takes care to
close them so that if you ask for 'xterm&' the rshd exits cleanly.