From: Scott Schwartz <schwartz@groucho.cs.psu.edu>
To: rsalz@osf.org
Cc: rc@hawkwind.utcs.toronto.edu
Subject: Re: rc and rsh
Date: Wed, 1 Jul 1992 16:59:30 -0400 [thread overview]
Message-ID: <92Jul1.170000edt.2538@groucho.cs.psu.edu> (raw)
In-Reply-To: Your message of "Wed, 01 Jul 92 15:13:11 EDT." <9207011913.AA00693@earth.osf.org>
| 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.
next prev parent reply other threads:[~1992-07-01 21:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1992-07-01 19:13 rsalz
1992-07-01 20:59 ` Scott Schwartz [this message]
1992-07-01 20:49 Donn Cave
1992-07-01 20:58 rsalz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=92Jul1.170000edt.2538@groucho.cs.psu.edu \
--to=schwartz@groucho.cs.psu.edu \
--cc=rc@hawkwind.utcs.toronto.edu \
--cc=rsalz@osf.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).