UNIX for Dummies Questions & Answers

Well it will only be slow once, until you clear out the junk! ;-)

I am on this for 5 hrs now and it is reducing very slowly.

Hence, need a quicker solution !!!

5 hours!? That doesn't seem right. I'm out of suggestions though. Are you sure there are no other processes using resources and thus slowing you down? Maybe you would be better doing this after hours when there is less load on the system?

Hopefully someone will have another suggestion.

The below is the command i am executing and a few errors along with the deletion that it is doing gradually.

Code:

find /apps/server -mtime +7 -exec rm -f {} ; &
 
 
find: stat() error /apps/server/G7654812_2011.12.01.03.05.55_Remittance.txt: No such file or directory
find: stat() error /apps/server/G7656084_2011.12.01.03.06.08_Remittance.txt: No such file or directory
find: stat() error /apps/server/G7655363_2011.12.01.03.06.09_Remittance.txt: No such file or directory
find: stat

Could this be the cause ? If so.. how can it be overcome... What the solution ?

Well, assuming no filesystem issues, and the file it is finding is indeed there and older than 7 days, you need a backslash in front of the semi-colon and I would restrict the search to files by using -type:

Code:

find /apps/server -type f -mtime +7 -exec rm -f {} \; &

---------- Post updated at 03:34 PM ---------- Previous update was at 03:27 PM ----------

Just thought of something. Are there sub-directories? If so, find is looking in each sub-directory too. I had this issue myself recently where I needed to restrict find to the top directory. Have a look at this, maybe it will help:
https://www.unix.com/unix-dummies-que...lp-needed.html
The last post summarizes what I ended up doing. To restrict to the highest directory (this is untested):

Code:

find /apps/server/* -type d -prune -o -type f -mtime +7 -exec rm -f {} \; &

Gary

This does not help either.. .seems I am getting the same output and the same slow crawling deletion.

Please see my edit above. And please just do a

Code:

-print

before doing the

Code:

rm

to make sure find is finding what you expect!