From owner-freebsd-hackers Thu Jul 20 07:56:34 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id HAA10473 for hackers-outgoing; Thu, 20 Jul 1995 07:56:34 -0700 Received: from haywire.DIALix.COM (haywire.DIALix.COM [192.203.228.65]) by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id HAA10466 for ; Thu, 20 Jul 1995 07:56:27 -0700 Received: (from peter@localhost) by haywire.DIALix.COM (8.6.12/8.6.12/DIALix) id WAA03035; Thu, 20 Jul 1995 22:56:19 +0800 Date: Thu, 20 Jul 1995 22:56:19 +0800 (WST) From: Peter Wemm To: hackers@freebsd.org Subject: timeouts on 'netstat' for address->name lookups? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: hackers-owner@freebsd.org Precedence: bulk When doing a 'netstat' or 'netstat -r', sometimes you can get 75 second timeouts on strange addresses that are not correctly configured in the dns (such as lame delegations). 'w' was recently changed so that it only spends up to two seconds trying to translate the address in the ut_host field into a name. Who would object to me doing the same to netstat? Even though it's a short timeout, the name server will continue to attempt to look up the name on your behalf. If it has trouble, and takes 10 or 20 seconds to resolve the name it will cache it. Subsequently running netstat again will show the real name, rather than the IP address. I ask, rather than 'just doing it', because it causes a small diversion from traditional behavior. I think it's useful. I like to see hostnames, but dont like 75 second timeouts. Using the -n switch looses all hostnames, and the port names, whereas this timeout will tell you what is available. Objections? It's 4 lines of code to add. -Peter