0000866: [PATCH] find returns 0 when no file is matched

BusyBox Bug and Patch Tracking

Viewing Issue Simple Details [ Jump to Notes ]

[ View Advanced ] [ Issue History ] [ Print ]

Category

Severity

Reproducibility

Date Submitted

Last Update

0000866

[BusyBox] Standards Compliance

minor

always

05-04-06 23:32

06-11-06 13:50

Reporter

asierllano

View Status

public

Assigned To

BusyBox

Priority

normal

Resolution

won't fix

Status

closed

Product Version

1.1.x

Summary

0000866: [PATCH] find returns 0 when no file is matched

Description

Execute:
find -name idontexist
echo $?

You will see that in busybox it returns 0, but in findutils it returns 1.

I've provided a simple patch that solves it easily.
This bug happens in the SVN snapshot, but I haven't tried to apply this patch to it, but it may apply directly or near-directly.

Additional Information

Attached Files

busybox-find-nomatch.patch [^] (1,327 bytes) 05-04-06 23:32

Relationships

Notes
(0001416) bernhardf 06-11-06 10:43	While i can see why returning a failure-code in this case would make sense, GNU find does return success too.

(0001424) vapier 06-11-06 13:50	findutils does not behave the same way on my machine as you say $ rm -rf foo $ mkdir foo $ find foo -name alsdf $ echo $? 0

Issue History
Date Modified	Username	Field	Change
05-04-06 23:32	asierllano	New Issue
05-04-06 23:32	asierllano	Status	new => assigned
05-04-06 23:32	asierllano	Assigned To	=> BusyBox
05-04-06 23:32	asierllano	File Added: busybox-find-nomatch.patch
06-11-06 10:43	bernhardf	Note Added: 0001416
06-11-06 13:50	vapier	Note Added: 0001424
06-11-06 13:50	vapier	Status	assigned => closed
06-11-06 13:50	vapier	Resolution	open => won't fix