All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: landley@webofficenow.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Hour long timeout to ssh/telnet/ftp to down host?
Date: Tue, 12 Jun 2001 19:18:03 -0700	[thread overview]
Message-ID: <3B26CD5B.47002360@candelatech.com> (raw)
In-Reply-To: <01061217025700.02061@localhost.localdomain>

Rob Landley wrote:
> 
> I have scripts that ssh into large numbers of boxes, which are sometimes
> down.  The timeout for figuring out the box is down is over an hour.  This is
> just insane.
> 
> Telnet and ftp behave similarly, or at least tthey lasted the 5 minutes I was
> willing to wait, anyway.  Basically anything that calls connect().  If the
> box doesn't respond in 15 seconds, I want to give up.
> 
> Is this a problem with the kernel or with glibc?  If it's the kernel, I'd
> expect a /proc entry where I can set this, but I can't seem to find one.  Is
> there one?  What would be involved in writing one?
> 

You can tune things by setting the tcp-timeout probably..I don't
know exactly where to set this..

You probably don't want all tcp to time out at 15 seconds anyway, so
I'd suggest either using non-blocking connect (if you have the code
that does the connect), or just set a timer (or use sigalarm) when you
start the attempt, and fail the attempt if the timer or alarm signal
goes off.

> If it's glibc I'm probably better off writing a wrapper to ping the
> destination before trying to connect, or killing the connection after a
> timeout with no traffic.  But both of those are really ugly solutions.

Ugly is relative, and don't use ping because there is still a race condition
(ping worked, but by the time you try tcp, the box is down.)

> 
> Anybody have any light to shed on the situation?
> 
> Rob
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

-- 
Ben Greear <greearb@candelatech.com>          <Ben_Greear@excite.com>
President of Candela Technologies Inc      http://www.candelatech.com
ScryMUD:  http://scry.wanfear.com     http://scry.wanfear.com/~greear

  reply	other threads:[~2001-06-13  2:18 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 [this message]
2001-06-12 21:47   ` Rob Landley
2001-06-13  9:40   ` Luigi Genoni
2001-06-13 10:07     ` 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=3B26CD5B.47002360@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=landley@webofficenow.com \
    --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.