If you really want to interact with the sftp cli, I think Expect is nearly always a better choice than IPC::Open2 or IPC::Open3. That being said, however, there is an sftp option that can make this a lot easier with just backticks...

open( OUT, ">/tmp/sftp-batch" );
print OUT <<"END";
cd foo
ls
END
close( OUT );

chomp( my @files = `sftp -b /tmp/sftp-batch hostname` );
open(OUT, ">/tmp/sftp-batch-2" );
print OUT <<"END";
cd foo
lcd bar
END
for my $file ( @files ) {
    print OUT "get $file\n";
}

system( "sftp -b /tmp/sftp-batch-2 hostname" );

[download]
We're not surrounded, we're in a target-rich environment!

In reply to Re: Short example using IPC::Open2 or IPC::Open3 by jasonk
in thread Short example using IPC::Open2 or IPC::Open3 by Limbic~Region

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.