Date: Mon, 29 Nov 2010 14:15:14 -0800 From: Garrett Cooper <gcooper@FreeBSD.org> To: Matthew Jacob <mj@feral.com> Cc: freebsd-hackers@freebsd.org Subject: Re: find(1): Is this a bug or not? Message-ID: <AANLkTinZvVoSyoBJm6E2mSHSom7JhMjyMLaHdg-=5Bf4@mail.gmail.com> In-Reply-To: <4CF40F8F.30303@feral.com> References: <86r5e3zye4.fsf@pluton.xbsd.name> <4CF40F8F.30303@feral.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Nov 29, 2010 at 12:39 PM, Matthew Jacob <mj@feral.com> wrote:
> 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.
I thought I had seen something similar to this in the past, but I
can't reproduce it with simple cases:
$ find .
.
./cant-touch-this
find: ./cant-touch-this: Permission denied
./hello-world
./hello-world/are-you-sure
$ find . -name '*'
.
./cant-touch-this
find: ./cant-touch-this: Permission denied
./hello-world
./hello-world/are-you-sure
$ find . -type f
find: ./cant-touch-this: Permission denied
./hello-world/are-you-sure
$ sudo find . -type f
./cant-touch-this/mchammer
./hello-world/are-you-sure
Thanks,
-Garrett
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTinZvVoSyoBJm6E2mSHSom7JhMjyMLaHdg-=5Bf4>