From owner-freebsd-bugs Sat May 13 15:39:04 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id PAA14261 for bugs-outgoing; Sat, 13 May 1995 15:39:04 -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 PAA14255 for ; Sat, 13 May 1995 15:39:02 -0700 Message-Id: <199505132239.PAA14255@freefall.cdrom.com> Received: by crh.cl.msu.edu (1.38.193.4/16.2) id AA23977; Sat, 13 May 1995 18:38:55 -0400 From: Charles Henrich Subject: Re: bin/402: w -n doesnt work as advertised. To: davidg@Root.COM Date: Sat, 13 May 1995 18:38:55 -0400 (EDT) Cc: henrich@crh.cl.msu.edu, freebsd-bugs@freefall.cdrom.com In-Reply-To: <199505132237.PAA00131@corbin.Root.COM> from "David Greenman" at May 13, 95 03:37:28 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 872 Sender: bugs-owner@FreeBSD.org Precedence: bulk > This works if the nameserver for all the domains is currently reachable. If >it isn't, it can take a minute for the query to timeout. About half the time I >do a 'w' on freefall, it takes > 1 minute to complete because of this. In >other cases, it's often that nameservers are slow to respond - 2 seconds isn't >unusual for non-cached entries. If this happens with just a few of the users, >the delay can approach 5-10 seconds. The problem grows as the number of users >increases. It's extremely annoying. Thats true, but if the user has logged in, they have caused their entry to be cached at the local nameserver, so you should very rarely be going offsite to get the data.. Unless something is broken in the local nameserver. -Crh Charles Henrich Michigan State University henrich@crh.cl.msu.edu http://rs560.msu.edu/~henrich/