🚀 go-pugleaf

Has anybody out there come across the error in xterm which causes it
to hang up when the child process exits, if xterm does not have a
controlling tty?  The scenario:

2 machines, alpha and beta.
We log in on alpha, fire up xinit, etc, and get an xterm on alpha.
we run "xhost beta"
we run  "rsh beta -n xterm alpha:0".
xterm fires up, and we do some stuff in the c-shell inside.
Now, we hit control-d (or exit, or logout, for that matter) to the
shell in the xterm running on beta, and the whole xterm freezes.  The
process has hung, and we can't kill it, even, short of rebooting beta.
This ONLY happens when we run xterm via rsh.  When we run xterm from a
login shell, or from another xterm, this doesn't happen.  Any ideas?
Alternately, does anybody out there NOT experience this problem?  It
occurs with releases 3 and 4 of the server, but with only release 4 of
the xterm.  release 3 xterm works fine.  We are running on 4.3bsd
uVaxen, sun3 (os 3.2), ibmRT(with kernel mods for X), and a Gould
UTX/32 (os 1.3).  Any ideas, anybody?
	--chet--
In Real Life:		Chet Murthy
ARPA:			murthy@svax.cs.cornell.edu
SnailMail:		Chet Murthy
			Gaslight Village Apts 21-B
			Uptown Road
			Ithaca, NY 14850
MaBellNet:		(607)-257-5709


-- 
	--chet--
In Real Life:		Chet Murthy
ARPA:			murthy@svax.cs.cornell.edu
SnailMail:		Chet Murthy
			Gaslight Village Apts 21-B
			Uptown Road
			Ithaca, NY 14850
MaBellNet:		(607)-257-5709