Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!cs.utexas.edu!asuvax!noao!stsci!schiffer
From: schiffer@stsci.EDU (Skip Schiffer)
Newsgroups: comp.sys.mac.comm
Subject: Re: Eudora POP mail client and A/UX 2.0
Message-ID: <2374@stsci.EDU>
Date: 19 Mar 91 11:49:18 GMT
References: <27DE8919.1A30@intercon.com> <1991Mar13.223450.20337@ux1.cso.uiuc.edu> <1991Mar14.154311.14616@casbah.acns.nwu.edu> <1991Mar15.024642.13733@ux1.cso.uiuc.edu> <2369@stsci.EDU> <18640@milton.u.washington.edu>
Reply-To: schiffer@stsci.EDU (Skip Schiffer)
Distribution: na
Organization: Space Telescope Science Institute, Baltimore, MD 21218
Lines: 25

In article <2369@stsci.EDU> schiffer@stsci.EDU (Skip Schiffer) writes:
>...using NCSA Telnet with MacTCP can result in a crash and burn of the Mac
>if you have the following scenario:

	The system is an SE/30, system 6.0.5, using multifinder, NCSA Telnet
2.4 beta 9, MacTCP 1.0.1 and an Ether+ SCSI Ethernet box.  The crashs are 
approximately 80% with both a Sun Unix box (BSD? Unix) and VAX with Mulitnet.
Note none of the crashes are immediate.  The only _safe_ manner I have found
to eliminate the extra sessions is to log into the VAX with the LAT 
connection tool and either kill the session on the VAX or "Set host" to the
Unix box and kill the session.  Provided Telnet is not running, there is no
crash. (if it is open with no sessions the system crashes when you open a
session.)

	The 80% figure is what makes me assume that the problem is likely 
to be the timing one which Steve points out.  Note that both the VAX and the
SUN are usually very heavily loaded, whereas my SE/30 normally does not have
any background processing occuring.  In addition the fact that I use the LAT
tool through the Ethernet box sort of exonerates the everything downstream of
MacTCP.

-- 
| F. H. Schiffer 3rd              |                            |
| schiffer@stsci.edu              | I speak for myself alone.  |
| scivax::schiffer                |                            |