From: "Nivedita Singhvi" <nivedita@us.ibm.com>
To: landley@trommello.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: tcp_keepalive_intvl vs tcp_keepalive_time?
Date: Sun, 10 Feb 2002 10:10:15 +0530 [thread overview]
Message-ID: <OF46DAF8B5.5C736002-ON65256B5C.0018A2C8@boulder.ibm.com> (raw)
> Would someone be kind enough to explain the difference between
> tcp_keepalive_intvl and tcp_keepalive_time?
> Documentation/filesystems/proc.txt says tcp_keepalive_time is the
interval
> between sending keepalive probes, but doesn't mention
tcp_keepalive_intvl...
tcp starts a keepalive timer for each connection. if the connection is idle
for tcp_keepalive_time seconds, it starts sending probes to the other end.
It sends a maximum of tcp_keepalive_probes each tcp_keepalive_intvl
seconds apart, and if the other end hasnt responded by then, it drops the
connection.
default values:
tcp_keepalive_intvl = 75 seconds
tcp_keepalive_probes = 9
tcp_keepalive_time = 7200 seconds (2 hours)
> The problem I'm trying to track down is ssh connections where the
connection
> times out but the session doesn't go away until a key is pressed. (I.E.
> blocking reads don't notice the connection going down underneath them,
not
> even if left overnight.)
not clear from the info here whats happening in your case...
(stats?)
> Rob
thanks,
Nivedita
next reply other threads:[~2002-02-10 4:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-10 4:40 Nivedita Singhvi [this message]
2002-02-10 7:56 ` [DOC PATCH] " Rob Landley
-- strict thread matches above, loose matches on Subject: below --
2002-02-08 23:42 Rob Landley
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=OF46DAF8B5.5C736002-ON65256B5C.0018A2C8@boulder.ibm.com \
--to=nivedita@us.ibm.com \
--cc=landley@trommello.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®