From owner-freebsd-hackers@FreeBSD.ORG Mon Nov 29 20:54:40 2010 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 867741065674 for ; Mon, 29 Nov 2010 20:54:40 +0000 (UTC) (envelope-from mj@feral.com) Received: from ns1.feral.com (ns1.feral.com [192.67.166.1]) by mx1.freebsd.org (Postfix) with ESMTP id 522368FC20 for ; Mon, 29 Nov 2010 20:54:40 +0000 (UTC) Received: from [192.168.221.2] (remotevpn [192.168.221.2]) by ns1.feral.com (8.14.4/8.14.3) with ESMTP id oATKdmdK039774 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Mon, 29 Nov 2010 12:39:50 -0800 (PST) (envelope-from mj@feral.com) Message-ID: <4CF40F8F.30303@feral.com> Date: Mon, 29 Nov 2010 12:39:43 -0800 From: Matthew Jacob Organization: Feral Software User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.12) Gecko/20101027 Thunderbird/3.1.6 MIME-Version: 1.0 To: freebsd-hackers@freebsd.org References: <86r5e3zye4.fsf@pluton.xbsd.name> In-Reply-To: <86r5e3zye4.fsf@pluton.xbsd.name> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender DNS name whitelisted, not delayed by milter-greylist-4.2.6 (ns1.feral.com [192.168.221.1]); Mon, 29 Nov 2010 12:39:51 -0800 (PST) Subject: Re: find(1): Is this a bug or not? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Nov 2010 20:54:40 -0000 can you report out the actual command line you're using and what release it's from? On 11/29/2010 12:08 PM, Denise H. G. wrote: > Hi, > > I found that, while searching for empty directories, find(1) will not > continue if it encounters a dir it can't enter (e.g. no privilege). I > don't know if it's so designed... I've checked NetBSD and OpenBSD's > implementations (almost identical to that of FreeBSD's). And they behave > the same way as FreeBSD's find(1) does under the circumstance. > > I'm wondering if this is a bug or not. >