Path: utzoo!attcan!uunet!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!mips!apple!snorkelwacker!bloom-beacon!LARRY.MCRCIM.MCGILL.EDU!mouse
From: mouse@LARRY.MCRCIM.MCGILL.EDU
Newsgroups: comp.windows.x
Subject: Re:  Why doesn't xterm -e rlogin us
Message-ID: <9009231709.AA03212@Larry.McRCIM.McGill.EDU>
Date: 23 Sep 90 17:09:40 GMT
Sender: root@athena.mit.edu (Wizard A. Root)
Organization: The Internet
Lines: 23

> Why would you want to run rlogin (usually TWO processes) if it works
> to simply run xterm on the remote host?

Well, the remote xterm doesn't always work, but that wasn't the
question you asked.  (And sometimes, even though a terminal emulator is
available remotely, one wants the local one for some reason - as, for
example, if the local machine is a DECstation, the remote is a Sun, and
one wants some feature that only dxterm has.)

Why?  Well, in my experience at least, it distributes the load
differently.  Running a terminal emulator on machine A and an rlogin
from A to B within it loads B less than running the emulator directly
on B.  If B is slower than A this means that the rlogin is a win.
(Presumably if B is loaded less then A is loaded more, but A was enough
faster than B in my case that I didn't notice any difference on A.)

					der Mouse

			old: mcgill-vision!mouse
			new: mouse@larry.mcrcim.mcgill.edu

(Rlogin also allows one to suspend the rlogin and return to the "local"
host, though presumably one could just start a local window.)