find error message ???

[MikeL_4]

When running the find command I am receiving the message:
Usage: find path-list [predicate-list]

command used:
if [ -d /Apps/applmgr/product/*/*/*/log ]; then /usr/bin/find -fsonly vxfs /Apps/applmgr/product/*/*/*/log -type f -mtime +30 -exec rm -f {} \; &
fi

Can you tell me what I'm doing wrong ???

Thanks

[Pete Randall · Accepted solution]

/usr/bin/find -fsonly vxfs /Apps/applmgr/product/*/*/*/log

should be
/usr/bin/find /Apps/applmgr/product/*/*/*/log -fsonly vxfs

Pete

[Patrick Wallek]

You've got to tell find where to look for the stuff you want to find as the first argument after find. I'm not sure it will work but your find should look like this:

/usr/bin/find /Apps/applmgr/product/*/*/*/log -type f -mtime +30 -fsonly vxfs -exec rm -f {} \;

I am not sure if the /Apps/applmgr/product/*/*/*/log will be a valid path for find. Try testing it first by replacing the 'rm -f' with a 'ls -l' in the -exec part of the command.

Good luck.

[S.K. Chan]

It's your syntax .. try this instead ..

/usr/bin/find /Apps/applmgr/product/*/*/*/log -fsonly vxfs -type f -mtime +30 -exec rm -f {} \; &

[Darren Prior]

Hi,

find requires the pathname to search down before any other arguments, as per the man page.

If you change your command to:

/usr/bin/find /Apps/applmgr/product/*/*/*/log -fsonly vxfs -type f -mtime +30 -exec rm -f {} \; &

you should have more luck. I'd test it withouth the -exec until you're happy though. You may also need to enclose the pathname in quotes, I've had issues with this before when using find / -name *.dat for example.

regards,

Darren.

[MikeL_4]

Right about now I am feeling rather stupid after looking over this for a couple of days and not noticing that.

Thanks..

[Pete Randall]

Ahhh, the obvious can be elusive sometimes, can't it? Don't feel stupid - we all end up needing a second opinion at one time or another.

Cheers,
Pete