From owner-freebsd-hackers Thu May 31 1: 2:13 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from dt051n37.san.rr.com (dt051n37.san.rr.com [204.210.32.55]) by hub.freebsd.org (Postfix) with ESMTP id A2B1937B423 for ; Thu, 31 May 2001 01:02:10 -0700 (PDT) (envelope-from DougB@DougBarton.net) Received: from DougBarton.net (master [10.0.0.2]) by dt051n37.san.rr.com (8.9.3/8.9.3) with ESMTP id BAA84558; Thu, 31 May 2001 01:01:55 -0700 (PDT) (envelope-from DougB@DougBarton.net) Message-ID: <3B15FA73.9EACFDEB@DougBarton.net> Date: Thu, 31 May 2001 01:01:55 -0700 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Dima Dorfman Cc: freebsd-hackers@freebsd.org Subject: Re: Problem with find -fstype local ? References: <20010531002416.EA6F03E0B@bazooka.unixfreak.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Dima Dorfman wrote: > > Doug Barton writes: > > Gang, > > > > This may be my lack of understanding, but doing 'find / -fstype local' > > is > > definitely traversing nfs mounted directories for me in -current and > > -stable. The man page isn't 100% clear, but it seems to me that it should > > not be doing that. My debugging got as far as determining that the option > > is being recognized in function.c before I ran out of time. A cursory > > examination didn't reveal to me any uses of the value that gets added to > > new->mt_data, but I didn't look very hard. > > > > This problem was brought to my attention by /etc/periodic/weekly/340.no > > id. > > If I am not correct about what this option really should be doing, for the > > record it'd be great to have an option for find that _does_ restrict paths > > to locally mounted directories. > > See PR 23906. This has been bugging me, too, but so far I've been too > lazy to fix it. Ok, the audit trail contains the fix, which I will apply post haste. Thanks for the response, it saves a lot of hair pulling on my part. At least now I know that the thing I was searching for really wasn't there. :) Doug To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message