Re: find(1): Is this a bug or not?

2010-12-02 Thread Ltr3z3r0n Llavtr3c
cool ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org

Re: find(1): Is this a bug or not?

2010-11-30 Thread Denise H. G.
On 2010/11/30 at 06:15, Garrett Cooper gcoo...@freebsd.org wrote: On Mon, Nov 29, 2010 at 12:39 PM, Matthew Jacob m...@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,

Re: find(1): Is this a bug or not?

2010-11-30 Thread Dag-Erling Smørgrav
Bakul Shah ba...@bitblocks.com writes: Index: function.c === --- function.c (revision 212707) +++ function.c (working copy) @@ -560,7 +560,7 @@ empty = 1; dir = opendir(entry-fts_accpath);

Re: find(1): Is this a bug or not?

2010-11-30 Thread Bakul Shah
On Tue, 30 Nov 2010 12:33:54 +0100 =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= d...@des.no wrote: Bakul Shah ba...@bitblocks.com writes: Index: function.c --- function.c (revision 212707) +++ function.c (working copy) @@ -560,7 +560,7 @@ empty = 1; dir =

Re: find(1): Is this a bug or not?

2010-11-30 Thread Dag-Erling Smørgrav
Bakul Shah ba...@bitblocks.com writes: Dag-Erling Smørgrav d...@des.no writes: You should replace the err() call with a warn() call instead of removing it outright. That would print the err msg twice as opendir (or something) already seems to report the error. Try it! Oh, OK. DES --

Re: find(1): Is this a bug or not?

2010-11-30 Thread Kevin Lo
Bakul Shah wrote: On Mon, 29 Nov 2010 12:39:43 PST Matthew Jacob m...@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): Is this a bug or not?

2010-11-29 Thread Denise H. G.
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

Re: find(1): Is this a bug or not?

2010-11-29 Thread Matthew Jacob
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

Re: find(1): Is this a bug or not?

2010-11-29 Thread Garrett Cooper
On Mon, Nov 29, 2010 at 12:39 PM, Matthew Jacob m...@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

Re: find(1): Is this a bug or not?

2010-11-29 Thread Bakul Shah
On Mon, 29 Nov 2010 12:39:43 PST Matthew Jacob m...@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