topic Re: find command in Operating System - HP-UX

find command

Ragni Singh — Mon, 28 Jan 2002 17:08:40 GMT

Hey guys,

what am I doing wrong here. I'm running this command and it doesn't seem to be doing what I'm asking.

find /home/jonny -name test.log.* -type f -mtime +14 -exec rm -f {} ;

I am running this out of my home directory. Trying to find for the file and remove it if the file hasn't been modified in over 14 days. Any help will be greatly appreciated.

Re: find command

Victor BERRIDGE — Mon, 28 Jan 2002 17:11:40 GMT

Hi
I think you forgot the backslash at the end of your line before the ;

All the best

Victor

Re: find command

James A. Donovan — Mon, 28 Jan 2002 17:12:26 GMT

try...
find /home/jonny -name "test.log.*" -a -type f -a -mtime +14 -exec rm -f {} \;

instead.

Re: find command

James R. Ferguson — Mon, 28 Jan 2002 17:14:00 GMT

Hi:

Do you have the backslash at the command's end (before the semicolon)?

# find /home/jonny -name test.log.* -type f -mtime +14 -exec rm -f {} \;

Regards!

...JRF...

Re: find command

harry d brown jr — Mon, 28 Jan 2002 17:14:15 GMT

Depending upon the shell, you should quote the name string because of the wild card.

find /home/jonny -name "test.log.*" -type f -mtime +14 -exec rm -f {} ;

live free or die
harry

Re: find command

Justo Exposito — Mon, 28 Jan 2002 17:14:52 GMT

Hi,

I Think that:
find /home/jonny -name "test.log.*" -a -type f -a -mtime +14 -exec rm -f {} \;

Regards,

Justo.

Re: find command

harry d brown jr — Mon, 28 Jan 2002 17:15:58 GMT

If you left off the backslash, then you would get this error:

find: -exec not terminated with ';'

Probably a bad cut and paste ;-)

live free or die
harry

Re: find command

David Navarro — Mon, 28 Jan 2002 17:16:07 GMT

Hi,
Try this:

find /home/jonny -name "test.log.*" -type f -mtime +14 -exec rm -f {} \;

Best luck

Re: find command

A. Clay Stephenson — Mon, 28 Jan 2002 17:18:34 GMT

Hi Sanman:

You have two problems:

1) As mentiopned you need the \ character before the ';'.

2) You need SINGLE QUOTES around your -n wildcard pattern because you do not want the shell toi expand the filename but rather you want to pass the wildcard string unmodified into find.

Regards, Clay

Re: find command

Bill Hassell — Mon, 28 Jan 2002 17:38:38 GMT

And as a debug note: NEVER include the -exec option (especially with rm -f) until you are sure the find actually returns the names you expect. A catastrophic result will take place if you accidently put a space in front of the * for your -name parameter!