Date: Mon, 21 Jun 2021 18:56:13 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 256755] /usr/bin/find -exec does not exit with non-zero exit status if appropriate Message-ID: <bug-256755-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D256755 Bug ID: 256755 Summary: /usr/bin/find -exec does not exit with non-zero exit status if appropriate Product: Base System Version: 12.2-STABLE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: bin Assignee: bugs@FreeBSD.org Reporter: sega01@go-beyond.org /usr/bin/find's manual page shows the following: -exec utility [argument ...] {} + Same as -exec, except that "{}" is replaced with as many path- names as possible for each invocation of utility. This behavi= our is similar to that of xargs(1). The primary always returns tr= ue; if at least one invocation of utility returns a non-zero exit status, find will return a non-zero exit status. However, find's behavior is different. $ find /var/empty -exec false {} \; ; echo $? 0 This doesn't seem to be in the spec, so I'm wondering if the man page is wr= ong, although personally I'd like this feature, or a flag to turn it on. https://stackoverflow.com/questions/14871147/how-to-exit-from-find-exec-if-= it-fails-on-one-of-the-files --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-256755-227>