Got a cronjob that downloads things regularly:if ! su scpuser -c scp ... > /dev/null 2>&1 || ! [ -f $scptarget ]; then;  error did not download stuff$scptarget is where the thing gets download to and it's on a different volume than the script that is running (but not a different state, same hard drive I think)Every time it errors out we go in and look and the file is there.  Is there a chance that the part that checks for the file's existence would succeed if it just chilled out a little bit?  Alternatively, could SCP be tossing errors even when it succeeded?  (I wish the guy who wrote this in the first place would have logged what the actual error was, I'm just kind of grasping at straws)If so, I don't want to add an arbitrary sleep to this script, is there something classier that real bash programmers do?
Is it possible to have a lag between scp and checking for new file
bash;files;scp