This sounds like... there should/could be some bash scripting here for reliability etc- rsync might have some features for you, - I know I know.. you're doing all this in perl. Thing is, some of what you talk about- these are problems that have come up for a lot of people, and custom software has been build tried and retested and rebuilt.. for making life easier.

Tell you what perl might be real good for here, holding everything together, maybe with a bunch of system, back tick calls.. etc. This will accept no user input, right?

Anyhow, I would seriously look into using as much of the existing system and shell utilities as possible. That would cut down on a lot of possible bugs.

In reply to Re: Net::FTP corrupting files or timing problem by leocharre
in thread Net::FTP corrupting files or timing problem by pattar_g

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.