If you are not limited in your ability to change the environment on either system to some degree, may I suggest using xinetd on the destination? You can define a port number in /etc/services and create a config entry for the daemon. Write a perl program to be invoked by the daemon for this service. This program will be started by xinetd with the incoming connection as stdin. It is pretty easy to pass across path/file/size, followed by the data. The source system perl script simply needs to connect to that system/port, provide the path/file/size, and then send the data. It is not secure, but if everything is within your firewalls, this might not be a problem. I use this approach all the time

In reply to Re: Problem with Net::SCP::Expect by Illuminatus
in thread Problem with Net::SCP::Expect by xorl

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.