From: "Eugene B. Berdnikov" <berd@elf.ihep.su>
To: kuznet@ms2.inr.ac.ru
Cc: linux-kernel@vger.kernel.org, davem@redhat.com
Subject: Re: Bug report: tcp staled when send-q != 0, timers == 0.
Date: Wed, 11 Apr 2001 22:50:51 +0400 [thread overview]
Message-ID: <20010411225051.B19364@elf.ihep.su> (raw)
In-Reply-To: <20010411011901.A2029@fay.elferno.lo> <200104111635.UAA08446@ms2.inr.ac.ru>
In-Reply-To: <200104111635.UAA08446@ms2.inr.ac.ru>; from kuznet@ms2.inr.ac.ru on Wed, Apr 11, 2001 at 08:35:51PM +0400
On Wed, Apr 11, 2001 at 08:35:51PM +0400, kuznet@ms2.inr.ac.ru wrote:
> To get this on new socket you should leave session idle for >2hours
> until the first keeplaive. After this it will never probe under
> any curcumstances. The bug was that keepalive corrupts state of timer
> and probe0 timer is not started after this.
Maybe. However, I did not understand, have you any reasonable explanation
how can I get such a socket. Indeed, I have been dealing with active
connection: I traced a squid redirector at a peak time of users web
activity. Several lines of log per second. That's why I was surprised
when this window become frozen.
If your model does not cover such situation, pls, take it in mind. :)
--
Eugene Berdnikov
next prev parent reply other threads:[~2001-04-11 18:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-09 14:43 Bug report: tcp staled when send-q != 0, timers == 0 Eugene B. Berdnikov
2001-04-10 17:38 ` kuznet
2001-04-10 21:19 ` Eugene B. Berdnikov
2001-04-11 10:16 ` Eugene B. Berdnikov
2001-04-11 16:56 ` kuznet
2001-04-11 18:35 ` Eugene B. Berdnikov
2001-04-11 19:04 ` kuznet
2001-04-11 19:28 ` Eugene B. Berdnikov
2001-04-11 19:37 ` kuznet
2001-04-11 16:35 ` kuznet
2001-04-11 18:50 ` Eugene B. Berdnikov [this message]
2001-04-11 19:09 ` kuznet
2001-04-11 19:18 ` Eugene B. Berdnikov
2001-04-13 8:54 ` Eugene B. Berdnikov
[not found] ` <200104181928.XAA04912@ms2.inr.ac.ru>
2001-04-21 15:45 ` Eugene B. Berdnikov
2001-04-21 17:02 ` kuznet
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010411225051.B19364@elf.ihep.su \
--to=berd@elf.ihep.su \
--cc=davem@redhat.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.