Date: Sat, 13 May 1995 15:43:36 -0700 From: David Greenman <davidg@Root.COM> To: Charles Henrich <henrich@crh.cl.msu.edu> Cc: freebsd-bugs@freefall.cdrom.com Subject: Re: bin/402: w -n doesnt work as advertised. Message-ID: <199505132243.PAA00153@corbin.Root.COM> In-Reply-To: Your message of "Sat, 13 May 95 18:38:55 EDT." <199505132239.PAA14255@freefall.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
>> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199505132243.PAA00153>