<p>Hmm. Somwone needs to update the rsync man pages to reflect -e default is ssh</p>
<div class="gmail_quote">On Dec 27, 2011 10:12 AM, "Brian Mathis" <<a href="mailto:brian.mathis%2Bale@betteradmin.com">brian.mathis+ale@betteradmin.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
There's no need for the -e stuff for a long time now. Rsync uses ssh<br>
by default on all modern versions. You get the same effect using the<br>
simpler form of:<br>
<br>
rsync -P file.to.transfer username@remote.host:/path/store/file/<br>
<br>
❧ Brian Mathis<br>
<br>
<br>
On Mon, Dec 26, 2011 at 11:44 PM, James Sumners <<a href="mailto:james.sumners@gmail.com">james.sumners@gmail.com</a>> wrote:<br>
> XMPP is really not the right tool for this. Rsync is what you want:<br>
><br>
> $ rsync -P -e "ssh -l username" file.to.transfer<br>
> remote.host:/path/store/file/<br>
><br>
> Where "username" is the SSH user you will be using to transfer the file.<br>
><br>
><br>
> On Monday, December 26, 2011, Wolf Halton <<a href="mailto:wolf.halton@gmail.com">wolf.halton@gmail.com</a>> wrote:<br>
>> What would be wrong with using xmpp as a transfer protocol for moving<br>
>> backups of tarred files? I have used scp for this purpose, but if the tunnel<br>
>> is broken, the file is corrupted. From what I have been reading, if a<br>
>> session drops in xmpp, it picks up where it was dropped and continues. I am<br>
>> working inside a c-class private subnet.<br>
>><br>
>> <a href="http://sourcefreedom.com" target="_blank">http://sourcefreedom.com</a><br>
<br>
_______________________________________________<br>
Ale mailing list<br>
<a href="mailto:Ale@ale.org">Ale@ale.org</a><br>
<a href="http://mail.ale.org/mailman/listinfo/ale" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a><br>
See JOBS, ANNOUNCE and SCHOOLS lists at<br>
<a href="http://mail.ale.org/mailman/listinfo" target="_blank">http://mail.ale.org/mailman/listinfo</a><br>
</blockquote></div>