Xref: utzoo comp.unix.ultrix:4865 comp.sys.mips:1090
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!uakari.primate.wisc.edu!bin
From: bin@primate.wisc.edu (Brain in Neutral)
Newsgroups: comp.unix.ultrix,comp.sys.mips
Subject: Re: TCP chokes between Ultrix 4 and 3.1c systems
Message-ID: <3246@uakari.primate.wisc.edu>
Date: 9 Oct 90 22:23:13 GMT
References: <lgy.655493851@newton>
Sender: bin@primate.wisc.edu
Reply-To: bin@primate.wisc.edu
Lines: 23

From article <lgy.655493851@newton>, by lgy@phys.washington.edu (Laurence G. Yaffe):
> gamiddle@maytag.waterloo.edu (Guy Middleton) writes:
>>Aha.  That seems to fix the problem.  I'll disable trailers on all our mips
>>boxes; they are evil in any case.
> 
>     Why?

I don't know the "official" answer, the the practical answer is:
precisely because they cause the kind of problems seen in this thread.
Not all implementations of TCP/IP know about them, and some handle them
badly, and you get crashed, hung or broken connections of all sorts.
Such as (this is what I've seen here, communicating with, e.g., 3b2's
or IBM mainframes):
	SMTP sessions that hang at the end, resulting in mail being
		sent over and over...
	NNTP sessions hanging forever
	etc.

--
Paul DuBois
dubois@primate.wisc.edu

                 "Was all of this because I wore a big man's hat?"