Path: utzoo!attcan!uunet!aplcen!wb3ffv!ssg0!petej
From: petej@ssg0.pharmacia.com (Peter M. Jansson)
Newsgroups: comp.windows.x
Subject: Re:  Why doesn't xterm -e rlogin us
Message-ID: <271@ssg0.pharmacia.com>
Date: 24 Sep 90 14:59:56 GMT
References: <9009231709.AA03212@Larry.McRCIM.McGill.EDU>
Reply-To: petej@ssg0 (Peter M. Jansson)
Organization: Pharmacia Diagnostics, Columbia, MD
Lines: 18

In article <9009231709.AA03212@Larry.McRCIM.McGill.EDU> mouse@LARRY.MCRCIM.MCGILL.EDU writes:
>> 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

On my system, at least two programs (telnet and u386mon) don't display
the characters unless run through an rlogin on an xterm.  That is, I
start X and I get an xterm (it's release 3, so I don't have xdm); to
get the dynamic, near-real-time status display from u386mon, I have to
do an rlogin.  Doesn't matter if I'm trying to get a display of the
local system or a remote system.

On the other hand, my rlogin doesn't seem to recognize SIGWINCH, so I
can't resize any windows.  Therefore, I occaisionally use rlogin for
those two programs, and just use an xterm otherwise.

	Pete.