[ale] [ot] Xmpp, ejabberd question

[Brian Mathis]

As of rsync 2.6 (1 Jan 2004)
    http://rsync.samba.org/ftp/rsync/src/rsync-2.6.0-NEWS

The man page since then has said (under SETUP):
    For remote transfers, a modern rsync uses ssh for its communications [1]
and the -e section says:
    Typically, rsync is configured to use ssh by default

-e can come in handy if you want to pass other options to ssh, such as
changing the port or encryption cipher.


[1] http://sunsite.ualberta.ca/Documentation/Misc/rsync-2.6.6/rsync.1.html#lbAF

❧ Brian Mathis


On Tue, Dec 27, 2011 at 10:15 AM, Jim Kinney <jim.kinney at gmail.com> wrote:
> Hmm. Someone needs to update the rsync man pages to reflect -e default is
> ssh
>
> On Dec 27, 2011 10:12 AM, "Brian Mathis" <brian.mathis+ale at betteradmin.com>
> wrote:
>> There's no need for the -e stuff for a long time now.  Rsync uses ssh
>> by default on all modern versions.  You get the same effect using the
>> simpler form of:
>>
>>    rsync -P file.to.transfer username at remote.host:/path/store/file/
>>
>> ❧ Brian Mathis
>>
>> On Mon, Dec 26, 2011 at 11:44 PM, James Sumners <james.sumners at gmail.com>
>> wrote:
>> > XMPP is really not the right tool for this. Rsync is what you want:
>> >
>> > $ rsync -P -e "ssh -l username" file.to.transfer
>> > remote.host:/path/store/file/
>> >
>> > Where "username" is the SSH user you will be using to transfer the file.
>> >
>> > On Monday, December 26, 2011, Wolf Halton <wolf.halton at gmail.com> wrote:
>> >> What would be wrong with using xmpp as a transfer protocol for moving
>> >> backups of tarred files? I have used scp for this purpose, but if the
>> >> tunnel
>> >> is broken, the file is corrupted. From what I have been reading, if a
>> >> session drops in xmpp, it picks up where it was dropped and continues.
>> >> I am
>> >> working inside a c-class private subnet.
>> >>
>> >> http://sourcefreedom.com