rm command is choking on large amounts of data?

sn9ke_eyes · 02-26-2003, 01:48 PM

Quote:

Originally posted by nxny
No offense, but the find command has been suggested in a previous post in this thread. I'd suggest reading the entire thread ( especially when it comes to threads small as this one ) before posting just so your post wouldn't appear redundant.

no offense, but I realize the find command has been suggested in a previous post in this thread. I'd suggest reading the entire thread so that you realize I am suggesting he use the -exec option for find instead of piping through xargs.

I'm not saying one way is better than the other, I'm just trying to provide the guy with more options.

nxny · 02-26-2003, 02:33 PM

Quote:

Originally posted by sn9ke_eyes
I'm not saying one way is better than the other, I'm just trying to provide the guy with more options. [/B]

Yup. But I was saying is that the find command ( with the exec rm {}\; ) will generate the very same error ( Arguments too long ) and hence is not an option.

xargs is the ONLY way out. Apart from splitting the search pattern and matching fewer files each time.

georgew · 02-27-2003, 10:46 PM

mv To move anything to /dev/null is a total process, and is completed, leaving a file of 0 bytes. Also cat /dev/null <file.name> cleans out the file, but the empty file remains with all of its previous permissions, useful for cleaning up cookies, browser droppings and log files. Its been far to long ago to remember, but was educated to believe that it was preferable to mv /dev/null rather than rm -rf

nxny · 02-28-2003, 07:11 PM

Quote:

Originally posted by georgew
Its been far to long ago to remember, but was educated to believe that it was preferable to mv /dev/null rather than rm -rf

Interesting. I would've never known.