From: Rick Jones <rick.jones2@hp.com>
To: Stephen Hemminger <shemminger@vyatta.com>
Cc: Adam Langley <agl@imperialviolet.org>,
Maxim Levitsky <maximlevitsky@gmail.com>,
netdev@vger.kernel.org
Subject: Re: How I can reset TCP sockets after long suspend/resume cyscle
Date: Wed, 04 Jun 2008 14:02:36 -0700 [thread overview]
Message-ID: <484702EC.30209@hp.com> (raw)
In-Reply-To: <20080604092154.7511c9d3@extreme>
While I know of at least one OS/stack which allows a root user to issue
a command to abort a TCP connection, (and it may be two given their
shared history) its use was always strongly discouraged.
> TCP should recover from this anyway. As soon as any activity happens
> on the connection the other end will respond with reset. For an IMAP
> session doing the next get-mail should cause a connection reset.
> Now it is possible that mail client has other problems.
And one way for there to be activity would be for the application(s) in
question to have an application-layer keepalive mechanism, or at the
very least, set SO_KEEPALIVE on their connections. And if they don't
want to rely on the sysadmin to have set what they consider a
"reasonable" value for when to start sending keepalive probes, a
TCP_KEEPIDLE setsockopt() perhaps.
rick jones
next prev parent reply other threads:[~2008-06-04 21:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-01 12:15 How I can reset TCP sockets after long suspend/resume cyscle Maxim Levitsky
2008-06-04 15:34 ` Maxim Levitsky
2008-06-04 16:09 ` Adam Langley
2008-06-04 16:21 ` Stephen Hemminger
2008-06-04 21:00 ` Maxim Levitsky
2008-06-04 21:02 ` Rick Jones [this message]
2008-06-04 20:52 ` Maxim Levitsky
2008-06-04 21:15 ` Stephen Hemminger
2008-06-04 21:23 ` Rick Jones
2008-06-05 21:31 ` Maxim Levitsky
2008-06-05 21:50 ` Rick Jones
2008-06-06 8:37 ` Benny Amorsen
2008-06-06 9:27 ` Nadejda Levitsky
2008-06-05 7:13 ` Evgeniy Polyakov
2008-06-05 21:19 ` Maxim Levitsky
2008-06-05 22:20 ` Evgeniy Polyakov
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=484702EC.30209@hp.com \
--to=rick.jones2@hp.com \
--cc=agl@imperialviolet.org \
--cc=maximlevitsky@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.com \
/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.