Thank you, I'll test that, then tell you if it worked.

Quoting Russ Allbery <r...@stanford.edu>:

Aurelin <aure...@aurelin.net> writes:

I'm trying to get around a problem with rsync and protocol 30.
I found out that if I try to do rsync over rssh with protocol 30, this  is
not working.
Command:
rsync rsshsynctest usr@vmsrv01:.
(It is equal to
rsync --protocol=30 rsshsynctest usr@vmsrv01:.
)

Yes, this is a known problem with the current release of rssh because
rsync reused the -e option as an internal flag to pass protocol
information in a particularly difficult way for what rssh is trying to
do.  You can get a patch that several of us *think* does the right thing
from various places, probably most easily:

    http://patch-tracker.debian.org/package/rssh/2.3.2-13

See fixes/rsync-protocol.diff.

--
Russ Allbery (r...@stanford.edu)             <http://www.eyrie.org/~eagle/>



Attachment: bine0lTlkj3MZ.bin
Description: PGP Public Key

Attachment: pgplgk218N6ss.pgp
Description: PGP Digital Signature

------------------------------------------------------------------------------
Index, Search & Analyze Logs and other IT data in Real-Time with Splunk 
Collect, index and harness all the fast moving IT data generated by your 
applications, servers and devices whether physical, virtual or in the cloud.
Deliver compliance at lower cost and gain new business insights. 
Free Software Download: http://p.sf.net/sfu/splunk-dev2dev
_______________________________________________
rssh-discuss mailing list
rssh-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rssh-discuss

Reply via email to