From owner-freebsd-stable  Fri Nov  8 05:49:10 1996
Return-Path: owner-stable
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id FAA04036
          for stable-outgoing; Fri, 8 Nov 1996 05:49:10 -0800 (PST)
Received: from time.cdrom.com (time.cdrom.com [204.216.27.226])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id FAA04028;
          Fri, 8 Nov 1996 05:49:08 -0800 (PST)
Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.8.2/8.6.9) with ESMTP id FAA04599; Fri, 8 Nov 1996 05:45:16 -0800 (PST)
To: Doug Rabson <dfr@render.com>
cc: wpaul@freebsd.org, dfr@freebsd.org, stable@freebsd.org
Subject: Re: Weirdie in mountd perhaps you can help me with... 
In-reply-to: Your message of "Fri, 08 Nov 1996 13:38:54 GMT."
             <Pine.BSF.3.95.961108133601.26390D-100000@minnow.render.com> 
Date: Fri, 08 Nov 1996 05:45:16 -0800
Message-ID: <4597.847460716@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-stable@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> Mountd wakes up when any filesystem (local or remote) is mounted so that
> it can correctly export local filesystems depending on the contents of
> /etc/exports.

Ah, OK, that makes sense..

> 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 :-(.

Understood.  It might also have been a transient error of other
origins.  I've still got the patient under guard and will report any
further suspicious behavior. :-)

I'll also try to figure out why I'm not getting argument values in
my stack traces.

						Jordan