I've been working with Net::SFTP for a while now, and had good success so far. However, I hit a speed bump in moving files to a host that uses the commercial SSH package from SSH.com. I wonder if anyone could share their experience with interop issues between Net::SFTP (and the underlying Net::SSH::Perl) and the SSH.com product.
In a nutshell, I call Net::SFTP::put() and check to see if the return value is undef. The module documentation says that this method returns undef on failure and a value that evaluates as true on success.
I am getting undef every time, but when I look on the remote server I see that the file does make the trip intact. Now I'm wondering if it this is a "normal" interop issue, or if there is something truly amiss. I looked in the online documentation at the SSH.com website, but didn't find a sufficient level of detail to answer the question.
I suppose I could fall back on a put()/stat()/proceed sequence that ignores the return value from put(), but that just doesn't seem as clean.
Anyone got experience, advice or humorous anecdotes to share on this?
Thanks!
In reply to Net::SFTP question: SSH.com interop by webengr
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |