Thanks for all the replies. The best of all possible worlds would be if we could control the FTP sender in addition to the receiver and just set up some handshake protocol there, but that'd make life too easy x). The poll-the-file-until-it-no-longer-changes is something that would most certainly work but it just feels a li'l brittle.
I've already implemented it using fuser
but the thought that the production machine's OS might not always have fuser
available crossed my mind and wouldn't let go (the warning in Linux::Fuser
stating that "even then it may not work on other than 2.2.* kernels" made me squirm a bit too).
In any case, fuser
seems to be working fine (though this thing is a bit awkward to test) . Once again, I've shamed my ancestors and forgotten to heed the potential wisdom of YouArentGonnaNeedIt
Thanks again for all the input!
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:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||