Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!samsung!think!mintaka!bloom-beacon!bu.edu!bu-cs!xylogics!world!spike
From: spike@world.std.com (Joe Ilacqua)
Newsgroups: comp.windows.x
Subject: Re: Remote xterm strategy
Message-ID: <1990Jan7.201628.556@world.std.com>
Date: 7 Jan 90 20:16:28 GMT
References: <90Jan6.054031est.2293@neat.cs.toronto.edu>
Organization: Software Tool & Die
Lines: 16


	You can reduce the number of process you have hanging around
by doing something like:

rsh host -n xterm -ls -display $DISPLAY '>&/dev/null </dev/null&'

	The magic incantations "-n" and "'>&/dev/null </dev/null&'"
cause rsh(1C) to exit.  This leave you with just the xterm and the
shell it started, and gets rid of the rsh and the shell rsh used to
start xterm.

	Is this faster?  I couldn't say...

->Spike
-- 
"The World" - Public Access Unix - +1 617-739-9753  24hrs {3,12,24}00bps