I've got a situation where I'm seeing hundreds of cp exec with "no such file or directory". I'm wondering what the best way to find out which file/path "cp" was initiating against so to rectify the problem or have the developer put in a fix to his/her application.
Sample output (this is a 120 second run):
errinfo -cn cp
EXEC SYSCALL ERR COUNT DESC
cp stat64 2 9 No such file or directory
cp open 2 10 No such file or directory
cp xstat 2 280 No such file or directory
Thanks in advance for any help.
I suppose that cp will check if the target exists before copying a file..
If you run
cp source destination
it will probably do 'stat' on 'destination', to ensure that the file doesn't exists before attempting the actually copy..