Any word on this? I'm having the exact same problem with a Backup
recipe I'm writing for Cap2... :-/
For now I'm creating my own string and calling a system("sftp
[EMAIL PROTECTED]:/some/big_file /some/large/target/big_file")
thanks,
Rogelio
p.s. I'm on cap trunk (7154)
On Jun 7, 10:21 am, Jamis Buck <[EMAIL PROTECTED]> wrote:
> You're right about thememoryconsumption for large files being due
> to Capistrano's interface. That could certainly be improved. But the
> wild CPU usage and slow upload speed is due toNet::SFTP(and to some
> extent,Net::SSH). Whatever you can come up with would be
> appreciated, certainly!
>
> - Jamis
>
> On Jun 7, 2007, at 8:50 AM, Mat Schaffer wrote:
>
> > On Jun 7, 2007, at 10:39 AM, Jamis Buck wrote:
> >> That would beNet::SFTP'sfault, and I'd certainly welcome any
> >> patches that madeNet::SFTPmore optimal. A word of caution,
> >> though...theNet::SFTPcode is...messy. It's pretty hard to follow,
> >> and I say that as the author of the library. I'm pretty embarrassed
> >> by bothNet::SSH andNet::SFTP.
>
> > Huh... that's not what I was expecting. I had assumed that the
> > nastiness was due to the fact that put took the full file contents as
> > an argument rather than streaming the file. I'll poke around a bit
> > more and send in patches if I have anything worth-while.
>
> > I just didn't want to start work that was doomed due to some kind of
> > best-practice that I didn't know about.
>
> > Thanks again, and didn't realize you wroteNet::SSH andNet::SFTP, so
> > thanks for that too. The interface kicks way more butt than any
> > other SSH library I've tried. Implementation can be fixed, api is
> > trickier. So I think you've done a fine job so far!
>
> > -Mat
--~--~---------~--~----~------------~-------~--~----~
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/capistrano
-~----------~----~----~----~------~----~------~--~---
