From owner-freebsd-bugs Sat May 13 18:49:44 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id SAA17401 for bugs-outgoing; Sat, 13 May 1995 18:49:44 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id SAA17395 for ; Sat, 13 May 1995 18:49:41 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id SAA01103; Sat, 13 May 1995 18:48:47 -0700 From: "Rodney W. Grimes" Message-Id: <199505140148.SAA01103@gndrsh.aac.dev.com> Subject: Re: bin/402: w -n doesnt work as advertised. To: henrich@crh.cl.msu.edu (Charles Henrich) Date: Sat, 13 May 1995 18:48:47 -0700 (PDT) Cc: davidg@Root.COM, henrich@crh.cl.msu.edu, freebsd-bugs@freefall.cdrom.com In-Reply-To: <199505132230.PAA14104@freefall.cdrom.com> from "Charles Henrich" at May 13, 95 06:30:25 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1425 Sender: bugs-owner@FreeBSD.org Precedence: bulk > > > > I modified w.c to attempt to figure out the ip address of the hosts > > > that were non-IP. Because some folks might need an option to make w > > > not do any resolver lookups, I also added -l which mirrors the > > > the existing -n flag, and ensures no nameserver calls get executed. > > > > Actually, I strongly dislike the 4.4 "w" doing nameserver lookups by > > default. On any reasonable system that has > 20 users on it, it can take > > anywhere from several seconds to several minutes for the w output to finish. > > In my opinion, the default for w should be reverted back to the old behavior > > of trusting what is in wtmp. > > Must be a slow nameserver? Most local nameervers will cache all retrieved data > for an hour to a day, given that the responses should 80% of the time come from > your local nameserver. I never have any problems with the lookups, w never > takes even a second to run. Try it on a box that has people coming in from behind firewalls, on freefall we have several users whos DNS reverse lookup is hidden by one thing or another and doing a ``w'' on freefall while one of them is logged in is quite painful. For machines that don't have such wide access you won't ever see this problem, but it does exist. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD