Re: Why has "find ... -exec rm -i '{}' ';'" stopped working?
Almut Behrens wrote:
>> I'm running "testing", and dpkg says I'm using bash 3.0-15 and findutils
>> 4.2.22-1.
>
> It seems to be a bug (or feature?) of find.
> (I can even reproduce the behaviour when moving the debian-testing find
> binary to a somewhat older SuSE box -- where the command in question
> does read from stdin otherwise)...
>
> Actually, it appears to be caused by a change in the upstream sources
> of find: comparing the respective strace outputs, one can observe
> that stdin in fact is being closed in the new (4.2.22) version before
> launching the child process rm -- while it is not in the old.
[snip details]
Interesting. So it is *not* (as I had assumed) something that I've changed
without realizing it.
> Well, I guess it's worth filing a bug report, to let the original
> authors figure out what it was that made them add this code -- and
> whether there is a way to work around the issue. Apparently, they
> didn't think anyone would ever want to do something like you do... ;)
I'll try that. Thanks!
Reply to: