From owner-freebsd-bugs Sat May 13 15:43:38 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id PAA14304 for bugs-outgoing; Sat, 13 May 1995 15:43:38 -0700 Received: from Root.COM (implode.Root.COM [198.145.90.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id PAA14298 for ; Sat, 13 May 1995 15:43:35 -0700 Received: from corbin.Root.COM (corbin.Root.COM [198.145.90.18]) by Root.COM (8.6.8/8.6.5) with ESMTP id PAA00538; Sat, 13 May 1995 15:46:41 -0700 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.11/8.6.5) with SMTP id PAA00153; Sat, 13 May 1995 15:43:37 -0700 Message-Id: <199505132243.PAA00153@corbin.Root.COM> To: Charles Henrich cc: freebsd-bugs@freefall.cdrom.com Subject: Re: bin/402: w -n doesnt work as advertised. In-reply-to: Your message of "Sat, 13 May 95 18:38:55 EDT." <199505132239.PAA14255@freefall.cdrom.com> From: David Greenman Reply-To: davidg@Root.COM Date: Sat, 13 May 1995 15:43:36 -0700 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. Again, not if the nameserver for a given zone is down. If it was down when they logged in and down when somebody does a "w", then there won't be any cached entry. named doesn't cache "timed-out" queries. -DG