CRC errors, retrying damaged files

I find that a fair number of files arrive corrupted, and i use a small script called retry which
does this...

#!/bin/sh
mysql ubhcache -pPASSWORD <<EOF
update headers set status="UNREAD" where subject like "%$1%" and subject like "%
$2%";
update assemble set status="COMPLETE" where status="FINISHED" and subject_part l
ike "%$1%" and subject_part like "%$2%";
select * from assemble where subject_part like "%$1%" and subject_part like "%$2
%";
EOF

This causes the file to be fetched again, and 9 times out of 10, the file arrives uncorrupted.
Sometimes the file has been expired from the server, and it is too late, so it would be
beneficial to automate this process, but of course the number of retrys would have to be limited
to avoid downloading the same file many many times if it cannot be fetched correctly.

I have noticed when watching ubh run, that sometimes it says a file has an incorrect CRC,
but i have not watched long enough to see if this always happens on corrupted downloads.

Has anyone tried any changes to automate retries?
If not, and suppose I find some time to look at it, does anyone know how reliable the error 
checking is?

Regards
Paul




------------------------ Yahoo! Groups Sponsor ---------------------~-->
Buy Ink Cartridges or Refill Kits for Your HP, Epson, Canon or Lexmark
Printer at Myinks.com. Free s/h on orders $50 or more to the US & Canada. http://www.c1tracking.com/l.asp?cid=5511
http://us.click.yahoo.com/l.m7sD/LIdGAA/qnsNAA/IHFolB/TM
---------------------------------------------------------------------~->

To unsubscribe from this group, send an email to:
[email protected]

 

Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/