public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rob Landley <landley@webofficenow.com>
To: Luigi Genoni <kernel@Expansa.sns.it>,
	Ben Greear <greearb@candelatech.com>
Cc: <landley@webofficenow.com>, <linux-kernel@vger.kernel.org>
Subject: Re: Hour long timeout to ssh/telnet/ftp to down host?
Date: Wed, 13 Jun 2001 06:07:49 -0400	[thread overview]
Message-ID: <01061306074902.00703@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.33.0106131138390.22415-100000@Expansa.sns.it>
In-Reply-To: <Pine.LNX.4.33.0106131138390.22415-100000@Expansa.sns.it>

On Wednesday 13 June 2001 05:40, Luigi Genoni wrote:
> On Tue, 12 Jun 2001, Ben Greear wrote:

> > You can tune things by setting the tcp-timeout probably..I don't
> > know exactly where to set this..
>
> /proc/sys/net/ipv4/tcp_fin_timeout
>
> default is 60.

Never got that far.  My problem was actually tcp_syn_retries. Remember, I was 
talking to a host that was unplugged.  (I wasn't even getting "host 
unreachable" messages, the packets were just disappearing.)  The default 
timeout in that case is rediculous do to the exponentially increasing delays 
between retries.  10 retries wound up being something like 20 minutes.

I set it to 5 and everything works beautifully now.  ssh (which retries the 
connection 4 times, and used to take over an hour to time out) now takes just 
over 3 minutes, which I can live with.

Rob

      reply	other threads:[~2001-06-13 15:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-12 21:02 Hour long timeout to ssh/telnet/ftp to down host? Rob Landley
2001-06-13  2:18 ` Ben Greear
2001-06-12 21:47   ` Rob Landley
2001-06-13  9:40   ` Luigi Genoni
2001-06-13 10:07     ` Rob Landley [this message]

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=01061306074902.00703@localhost.localdomain \
    --to=landley@webofficenow.com \
    --cc=greearb@candelatech.com \
    --cc=kernel@Expansa.sns.it \
    --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