??
Are you sure they were some file to move ?
Did you check you are granted to manipulate those files ?
make sure you are granted to write in the target directory
if the following command list the file you are looking for
the dot in find . means "the current dir you are in" so if your script does some cd <somewhere_else> , then your find command may be launched in a directory that does not contain any files you are looking for.
Please show us the full code of your script, and your operating system version (use command uname -a )
Please provide the full PATH of the directory you want to search in.
Please provide an example of absolute filename you have and want to be found.
Did you write your script directly in a unix editor, or did you wrote it into a Windows editor and then did a copy/paste ?
It looks as if you would have ^M stuff to remove from your file (such as it happens when things come from Windows.
---------- Post updated at 08:20 PM ---------- Previous update was at 08:10 PM ----------
Hi Scott
Yep i just noticed that
unfortunately i don't have an AIX machine around (linux Solaris and FreeBSD only) :o
But i found an AIX man xargs
I feel angry at myself not to be able to help ppl running a simple
find ...| xargs ...
but i still go on, i am sure we will get it working ! :D:D:D
Thanks for the guidance at my early stage of shell learning.
As I mentioned erlier after using tr the ^M error is gone but the find command in the script is still not executing inside the script but independently it is working...
Can you let me know the reason and solution to this
I would start by replacing cp with echo in the xargs command for debug.
What output is there? Is it running in a cronjob, or from the command line? What shell are you using? If possible post the entire script - or at least everything up to and including the find command.