Path: utzoo!utgpu!watmath!clyde!att!rutgers!mailrus!eecae!cps3xx!usenet
From: usenet@cps3xx.UUCP (Usenet file owner)
Newsgroups: comp.sys.ibm.pc.rt
Subject: Re: Inquieries for "Bad Aspects" of the RT
Message-ID: <1244@cps3xx.UUCP>
Date: 6 Dec 88 13:01:01 GMT
References: <139@icarus.kulcs.uucp>
Organization: Engineering, Michigan State U., E. Lansing MI
Lines: 22

in article <139@icarus.kulcs.uucp>, dannyb@kulcs.uucp (Danny Backx) says:
> 
> Indeed. I routinely use a telnet connection to work with an RT. This was
> absolutely impossible with 2.1.2. I think the Ethernet software was broken.
> (AIX 2.2 is better, but still not good.)
> What happens on 2.2: when a large amount of data is being sent to my terminal,
> (say the output of 'ls -l /etc'), the first part gets tru, then the output
> stops, and after a LONG time, it continues (also in bursts).
> I suspect the timeout strategy in TCP.

This probably isn't TCP's fault. I work on a 3162 async terminal
attached via an RS422 card to a Model 135 runnning AIX 2.2. I used to be
hooked to a Model 125 running AIX 2.1.2. The pause on long outputs
occurs on both these systems with no Ethernet involved. From what I saw,
long outputs should be feed to pg. The subsequent pause every page is
enough inactivity to avoid being swapped out as a result of alot of
output.

John H. Lawitzke      UUCP: ...rutgers!mailrus!frith!fciiho!jhl
Michigan Farm Bureau        ...decvax!purdue!mailrus!frith!fciiho!jhl
Insurance Group             ...uunet!frith!jhl
"What?!? Real computing at an insurance company?!? AND in Michigan!?!"