Search Results

Excellent, it has certainly improved things. I ran a test with a subset of data, the old script processed it in 210 minutes. The new script with the above code in it ran in 70 minutes - fantastic....

Ah, I see. That makes sense. Fantastic it could just do the trick. I will give it a whirl and report back.
Many thanks once again.

Sorry can you just explain the line -

(cd $Archive ; find . -type f )| xargs rm

I can see that you have copied the files into $Archive, along with its sub-directories. But then this line seems...

Guys, many thanks for your help here, it really is appreciated. I will have a go with your suggested work around.
And no we don't edit the script each day I was just filling a few parameters in to...

Sorry, I have probably confused things along the way.

Basically we have a file system which has numerous folders and sub-folders, and is populated each day by incoming systems. Each day we archive...

Ok point taken but in your script -

#! /usr/bin/ksh
(($#)) && mv "$@" /destination
exit 0


the destination is dependant on the path of each file being moved, I need to get that information...

Thanks again for that.

One final thing, at the moment the find is in a FOR loop and within that loop, prior to the move, it does a couple of checks for things like if the destination directory it...

Thanks for the advice on that. I am curious as to how this makes things faster as to all intents and purposes isn't it just doing a mv within the script the same as it would anyway?

Thanks for that. could you just explain in the script what (($#)) does.

Every day we back up all files on our system that are older than 7 days, so effectively we do a day's worth at a time.
The way we do this is to issue a find command using mtime +7 - we then loop...