🚀 go-pugleaf

	We are running both versions of telnet on our apollo net,
talking to VAX 11/750's running Ultrix, an 11/780 running VMS
and a MV10000 running DG/UX.

	Here's the problem, /usr/ucb/telnet talks to everybody fine,
hangs up after a session fine... But, /com/telnet is a different
story.  It will call any of the other machines fine, work fine
during the session and even close fine after a session to a unix
machine.  But to VMS, which is running EXCELAN telnet and ftp,
when I log out, the /com/telnet starts spitting out errors
"Remote machine reset connection" or something to that effect.
Trying to escape from /com/telnet then becomes an adventure,
Control-q won't work and any other key sequence just repeats
the error "Remote machine reset connection"... If I try to
sigp the process from another shell, it ignores it.  A sigp -B
from another shell causes any input to the locked window to
be completely ignored, and the process disappears from the
process list. But then the window can't be deleted (even
control-n is ignored).  Finally in desparation, I turned it
into an icon to keep it out of the way and it turned into
a graphics icon.  When I tried to log off it was unable to stop
all processes and I had to tell it to BLAST them.

What's the major difference between the two telnet utilities
(that question directed mostly towards any Apollo R&D's
listening).  I realize that the VMS telnet may be the one
messing up /com/telnet, but there should still be a way to
kill it without all this trouble.

Michael Burati
University of Lowell
CS Dept

UUCP:	{apollo | wanginst | masscomp | datacube}!ulowell!burati
CSNET:	burati@ulowell.csnet


ps:	I'm not unhappy with the software, in fact except for
this one problem, the net software has been perfect since we
got the sr9.2.3 version (sr9.0 tcp software gave me nightmares).