From owner-freebsd-hackers  Thu Jul 20 11:48:00 1995
Return-Path: hackers-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.11/8.6.6) id LAA18694
          for hackers-outgoing; Thu, 20 Jul 1995 11:48:00 -0700
Received: from eldorado.net-tel.co.uk (eldorado.net-tel.co.uk [193.122.171.253])
          by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id LAA18687
          for <hackers@freebsd.org>; Thu, 20 Jul 1995 11:47:55 -0700
From: FreeBSD@net-tel.co.uk
Received: (from root@localhost) by eldorado.net-tel.co.uk (8.6.12/8.6.10) id TAA04785 for hackers@freebsd.org; Thu, 20 Jul 1995 19:47:17 +0100
X400-Received: by mta "eldorado" in "/PRMD=net-tel/ADMD=gold 400/C=gb/"; 
        Relayed; Thu, 20 Jul 95 19:46:56 +0100
X400-Received: by mta "net-tel cambridge" in "/PRMD=net-tel/ADMD=gold 400/C=gb/";
         Relayed; Thu, 20 Jul 95 18:46:53 +0000
X400-Received: by "/PRMD=Net-Tel/ADMD=Gold 400/C=GB/"; Relayed; 
        Thu, 20 Jul 95 19:46:30 +0100
X400-MTS-Identifier: 
        ["/PRMD=Net-Tel/ADMD=Gold 400/C=GB/";hst:16488-950720184630-3201]
X400-Content-Type: P2-1984 (2)
X400-Originator: FreeBSD@net-tel.co.uk
Original-Encoded-Information-Types: IA5-Text
X400-Recipients: hackers@freebsd.org
Date: Thu, 20 Jul 95 19:46:30 +0100
Content-Identifier: Re: timeouts on 
Message-Id: <"hst:16488-950720184630-3201*/S=FreeBSD/O=NET-TEL Computer
 Systems Ltd/PRMD=Net-Tel/ADMD=Gold 400/C=GB/"@MHS>
To: hackers@freebsd.org
In-Reply-To: <"SunOS:3994-950720153445-0192*/DD.RFC-822=hackers-owner(a)freebsd.org/O=internet/PRMD=NET-TEL/ADMD=GOLD
 400/C=GB/"@MHS>
Subject: Re: timeouts on 'netstat' for address->name lookups?
Reply-To: Andrew.Gordon@net-tel.co.uk
Sender: hackers-owner@freebsd.org
Precedence: bulk

While 75sec may well be too long for netstat, 2sec timeout is too short
IMHO - your argument about nameservers assumes that you are runing a
nameserver locally.  If your nameserver is, for example, at the other end
of a dialup PPP link, the two second timeout would very frequently fail to
get the answer even when things were working normally [OK, I know I ought
to set up a caching-only nameserver on my machine at home, but I've never
got around to it...].

For me, somthing in the range 5-10 sec would be OK, though this feels like
the sort of issue where you can't find a value to please everybody.  And as
someone else said, there's always netstat -n....


Andrew.