From owner-freebsd-stable Fri Nov 8 16:35:50 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA22460 for stable-outgoing; Fri, 8 Nov 1996 16:35:50 -0800 (PST) Received: from salsa.gv.ssi1.com (salsa.gv.ssi1.com [146.252.44.194]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA22452; Fri, 8 Nov 1996 16:35:45 -0800 (PST) Received: (from gdonl@localhost) by salsa.gv.ssi1.com (8.7.5/8.7.3) id QAA21653; Fri, 8 Nov 1996 16:35:10 -0800 (PST) From: Don Lewis Message-Id: <199611090035.QAA21653@salsa.gv.ssi1.com> Date: Fri, 8 Nov 1996 16:35:09 -0800 In-Reply-To: Doug Rabson "Re: Weirdie in mountd perhaps you can help me with..." (Nov 8, 1:38pm) X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95) To: Doug Rabson , "Jordan K. Hubbard" Subject: Re: Weirdie in mountd perhaps you can help me with... Cc: wpaul@freebsd.org, dfr@freebsd.org, stable@freebsd.org Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Nov 8, 1:38pm, Doug Rabson wrote: } Subject: Re: Weirdie in mountd perhaps you can help me with... } > } > The corresponding mount request also succeeds at the end of this timeout. } > } > Any ideas? } } My guess is that it is trying to DNS resolve a badly formed address. The } timeouts for this are pretty long. Impossible to tell without knowing the } arguments to gethostbyaddr and res_query :-(. That would be my suspicion. Try: env RES_OPTIONS=debug mountd -d to turn on debugging in the resolver and enable the undocumented mountd debug mode so that it doesn't go into the background. --- Truck