From owner-freebsd-bugs Sat May 13 15:30:43 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id PAA14111 for bugs-outgoing; Sat, 13 May 1995 15:30:43 -0700 Received: from crh.cl.msu.edu (crh.cl.msu.edu [35.8.1.24]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id PAA14104 for ; Sat, 13 May 1995 15:30:41 -0700 Message-Id: <199505132230.PAA14104@freefall.cdrom.com> Received: by crh.cl.msu.edu (1.38.193.4/16.2) id AA23520; Sat, 13 May 1995 18:30:25 -0400 From: Charles Henrich Subject: Re: bin/402: w -n doesnt work as advertised. To: davidg@Root.COM Date: Sat, 13 May 1995 18:30:25 -0400 (EDT) Cc: henrich@crh.cl.msu.edu, freebsd-bugs@freefall.cdrom.com In-Reply-To: <199505132227.PAA01616@corbin.Root.COM> from "David Greenman" at May 13, 95 03:27:34 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 1038 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. -Crh Charles Henrich Michigan State University henrich@crh.cl.msu.edu http://rs560.msu.edu/~henrich/