in.rshd problems

Article View: comp.sys.sun

Article #10903

#10903

From: Alexander Dupuy
Date: Tue, 14 Feb 1989 08:25

12 lines
914 bytes

I don't know why in.rshd is so large, but you can eliminate it from being
a problem by running remote xterms like this:

csh% rsh server -n "xterm >&/dev/null &"

I wasn't able to get this to work right with ksh for whatever reason.

After starting up the remote xterm, the in.rshd will exit, and stop taking
up swap space.  You could redirect output from the xterm to a file if you
didn't want to lose it.

@alex

Technical Details

Message-ID: <8902081653.AA04498@cs.columbia.edu>

Path:

arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!nrl-cmf!ukma!rutgers!mit-eddie!uw-beaver!rice!sun-spots-request

Show Full Headers

Complete Article Headers

Path: arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!nrl-cmf!ukma!rutgers!mit-eddie!uw-beaver!rice!sun-spots-request
From: dupuy@cs.columbia.edu (Alexander Dupuy)
Newsgroups: comp.sys.sun
Subject: in.rshd problems
Message-ID: <8902081653.AA04498@cs.columbia.edu>
Date: 14 Feb 89 08:25:35 GMT
Sender: usenet@rice.edu
Organization: Sun-Spots
Lines: 12
Approved: Sun-Spots@rice.edu
Original-Date: Wed, 8 Feb 89 11:53:44 EST
X-Sun-Spots-Digest: Volume 7, Issue 152, message 8 of 9