From mboxrd@z Thu Jan  1 00:00:00 1970
To: 9fans@cse.psu.edu
From: "Douglas A. Gwyn" <DAGwyn@null.net>
Message-ID: <3B57454D.69E9F9E4@null.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <20010718230019.3004.qmail@g.bio.cse.psu.edu>, <Pine.BSO.4.33L2.0107191130590.15697-100000@spy.suspicious.org>
Subject: Re: Samterm panic (was Re: [9fans] sam vs acme)
Date: Fri, 20 Jul 2001 08:54:32 +0000
Topicbox-Message-UUID: d18c23a2-eac9-11e9-9e20-41e7f4b1d025

suspect@spy.suspicious.org wrote:
> samterm:panic: count>DATASIZE: Success

If I recall correctly, the last time I encountered this
was using a 630 on UNIX, and it turned out to be due to
the tty handler being switched back to cooked mode before
the sam front end had consumed all the data from the
final packet.  I changed the protocol to include one
extra handshake before both halves terminated.  If the
current "sam" is susceptible to this, I'd suggest the
same cure.