scp aborts when encountering a file witch it cannot get access to.
on host 1: /whatever/ contains ~10.000 files each 2-100kB in size daemons running on the host are creating new files in /whatever/ Creating a new file takes ~10 sec, and it happens every ~50 sec.
on host 2:
an hourly cronjob runs
scp -q me@host1:/whatever/* /local_copy_of_whatever/
scp fails when processing the files the the writing daemons is still accessing. I suspect that it is because it cannot gain access to the files being created. It seems as scp simply aborts in this situation. At the next run the problematic file will be copy'ed without any complains.
I would like a way to make scp ignore the problematic files - and continue quietly. (knowing that my cron job will get the file later)