logo       

Re: busybox 0.60.5 rm -rf has problems: msg#00156

linux.busybox

Subject: Re: busybox 0.60.5 rm -rf has problems

Dan Kegel <dank@xxxxxxxxx> writes:

> # rm -rf
> /home3/dank/wk/ixos/dap_interim/linux/3rdParty/crosstool/crosstool-0.15/build/sh4-unknown-linux-gnu/gcc-ss-3_3-20030714-glibc-2.2.5
> || echo fail
> rm: unable to stat
> `/home3/dank/wk/ixos/dap_interim/linux/3rdParty/crosstool/crosstool-0.15/build/sh4-unknown-linux-gnu/gcc-ss-3_3-20030714-glibc-2.2.5':
> File name too long
> fail
>
> Tsk. That seems to disobey SuSv3:
>
> -f
> Do not prompt for confirmation. Do not write diagnostic messages
> or modify the exit status in the case of nonexistent operands.

Nonexistent operand means error code ENOENT which actually is ignored
if -f is specified (see libbb/remove_file.c). But the returned error
code is ENAMETOOLONG, which is reported by rm and leads to a non zero
exit status.

regards,
Jean


<Prev in Thread] Current Thread [Next in Thread>
Google Custom Search

News | FAQ | advertise