From: spierce@wam.umd.edu (Stephen Pierce) Subject: Re: Problems with TCP/IP. Date: Sun, 28 Feb 1993 22:28:52 GMT
In article <1mrc33INN16p@crcnis1.unl.edu> hosier@unl.edu (aaron hosier) writes:
>spierce@wam.umd.edu (Stephen Pierce) writes:
>> Occationally (usually more frequent when I'm actually doing something
>>important <grin>) if I am networking into or out of the machine, the telnet
>>session will stop echoing characters. However, since once I got caught in a
>>talk with my self and it happened, I know that the remote system gets the
>>characters, but the host system does not receive them.
>>Steve
>
>I guess you could add me also to this category. The sessions seem to
>lock up, but actually just stop echoing what I type and what is sent by
>the other computer. I admit that it has greatly improved under 99pl5,
>but still occurs once in a while. Someone one mentioned something about
>ttys not being flushed, which would account for what happens after a
>lock up. If it was a telnet session, and it lockes up, I type logout,
>I log out of the other maching, and as soon as I get back to Linux, all
>the characters I've been typing but couldn't see come through.
At last, someone who is having the same problem as I. I wonder why
no body else has experienced the problem? It's quite annoying to me and
all my users, and I hope to get it fixed, but alas I am not competent
to debug TCP/IP. I can and have written in C for the last 4 years, and I need
some help to figure out what's happening here.
What I really want to know, is how do I go about diagnosing the problem?
That way I can do 99% of your (TCP/IP kernal maintainer) work, and this
bug can get squashed. If anyone can give me advice, please send it in
e-mail.
Steve