topic Re: find command: replace exec to xargs problem in Operating System - HP-UX

find command: replace exec to xargs problem

Ho_5 — Fri, 21 Mar 2003 11:30:56 GMT

Hi,

I want to replace the exec to xargs in find command, because every time when I run the command CPU is overloaded.

find . -name "*.day.*" -exec cp -r {} /store \; -exec rm -f {} \;

Re: find command: replace exec to xargs problem

Pete Randall — Fri, 21 Mar 2003 11:39:55 GMT

I'm not sure how you would chain the two commands together without repeating the find, but using find with xargs is easy:

find . -name "*.day.*" |xargs cp -r;find . -name "*.day.*" |xargs rm -f

Pete

Re: find command: replace exec to xargs problem

Ho_5 — Fri, 21 Mar 2003 11:47:38 GMT

thanks, but it should not work

I try to change it into the next syntax, but the CPU load still HIGH.

find . -name "*.day.*" | xargs -i cp -r "{}" /store | xargs -i rm -f

By the way, do I need to use -i and "{}"???

Regards,

John

Re: find command: replace exec to xargs problem

Pete Randall — Fri, 21 Mar 2003 11:53:15 GMT

I'm curious - does running the find command by itself increase your CPU load?

find . -name "*.day.*"

Pete

Re: find command: replace exec to xargs problem

John Poff — Fri, 21 Mar 2003 12:02:03 GMT

Hi,

How many files and directories are in the directory tree at the point where you run the find command?

JP

Re: find command: replace exec to xargs problem

Ho_5 — Fri, 21 Mar 2003 12:03:47 GMT

The problem is on every half of hour there are two find command's in two different scripts running.
It looks like running 2 find command in the same time, it will generate CPU overload.
Reschedule the scripts in the crontab is not possible.
So any idea how to rebuild the find command??

Re: find command: replace exec to xargs problem

Ho_5 — Fri, 21 Mar 2003 12:05:51 GMT

more than 100 hundred at least..

Re: find command: replace exec to xargs problem

Robin Wakefield — Fri, 21 Mar 2003 12:16:18 GMT

Hi

How about trying:

find . -name "*.day.*" | xargs -i echo "cp -r {} /store;rm -f {}" |sh

rgds, Robin.

Re: find command: replace exec to xargs problem

David_246 — Fri, 21 Mar 2003 12:21:20 GMT

Hoi Ho,

Why don't you do the following :

for i in `find ./ -name "*.day.*"`
do
cp -r $i /store
rm -f $i
done

Groeten/Regs,
David

Re: find command: replace exec to xargs problem

David_246 — Fri, 21 Mar 2003 12:24:27 GMT

Uhh,

What about :

find ./ -name "*.day.*" -exec mv {} /store \;

Regs David

Re: find command: replace exec to xargs problem

Ho_5 — Fri, 21 Mar 2003 12:38:08 GMT

hmmmm mv command.

find ./ -name "*.day.*" -exec mv {} /store \;

If I translate it into xargs. should it be like this??

find . -name "*.day.*" | xargs -i mv ./{} /store/{}

The advantage of using "xargs" instead of "exec" is that it save the CPU time or not? if you have a lot of file to find. please confirm this

John

Re: find command: replace exec to xargs problem

James R. Ferguson — Fri, 21 Mar 2003 12:53:16 GMT

Hi Ho:

The advantage to 'xargs' over 'exec' in situations like you describe is really two-fold. First, you avoid the potential for an "argument list too long". Secondly, and more importantly, you avoid forking a separate task for every argument processed.

Another often overlooked ability of 'xargs' to bundle, as many arguments as specified by its '-n number' option together into a single execution.

Regards!

...JRF...

Re: find command: replace exec to xargs problem

Donny Jekels — Fri, 21 Mar 2003 13:56:45 GMT

there,

this works.

find ./ -name \*.day.\* -exec /usr/bin/mv {} /store \;

Re: find command: replace exec to xargs problem

John Bolene — Fri, 21 Mar 2003 14:33:10 GMT

find is a pig no matter what you do with it

it has to traverse the I/O super block tables and find what you are looking for

you can nice this process so that it gets whatever cpu is left over

you can cd to the directory you are finding stuff in and then do the find

you have to find (pun intended) ways to reduce the number of I/O trees that the command is searching thru to find what you want