Use two passes. In the first pass over the directory, make a list of all files in the directory and their size. Ten minutes later, if that size hasn't changed, move them to wherever it is you want.

The logic, in more detail, might look like this:

This doesn't guarantee the tar's aren't corrupt, but it does at least give them time to finish being sent.

Update:

Another strategy might be to attempt to get a flock on the tar. I'm suggesting this under the assumption that the FTP server locks the file while it's still being written to. If that's the case, you won't be able to get a flock on the file while it's being uploaded. And that will tell you whether or not it's safe to process it.


Dave


In reply to Re: How to handle broken tars ? by davido
in thread How to handle broken tars ? by SpaceCake

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.