My remote server runs gentoo x86. My client machine runs ~x86. When trying to access the remote server using rsync, I get: $ rsync -e ssh -Cavbz dir user@foo:public_html/ Password: filter rules are too modern for remote rsync. rsync error: syntax or usage error (code 1) at exclude.c(1119) $ On remote server I have: # rsync --version rsync version 2.6.0 protocol version 27 Copyright (C) 1996-2004 by Andrew Tridgell and others <http://rsync.samba.org/> Capabilities: 64-bit files, socketpairs, hard links, symlinks, batchfiles, IPv6, 64-bit system inums, 64-bit internal inums On local client I have: $ rsync --version rsync version 2.6.4 protocol version 29 Copyright (C) 1996-2005 by Andrew Tridgell and others <http://rsync.samba.org/> Capabilities: 64-bit files, socketpairs, hard links, symlinks, batchfiles, inplace, no IPv6, 64-bit system inums, 64-bit internal inums
if you upgrade your server to 2.6.4 does it work ? what if you downgrade your client to 2.6.0 ?
It also happens to me when I want to connect using the 2.6.4 client to 2.5.5 server on Tru64Unix 5.1 (OSF1): $ rsync --version rsync version 2.5.5 protocol version 26 Copyright (C) 1996-2002 by Andrew Tridgell and others <http://rsync.samba.org/> Capabilities: 64-bit files, socketpairs, hard links, symlinks, batchfiles, no IPv6, 32-bit system inums, 64-bit internal inums Yes, upgrading remote server to 2.6.4 helps and I can rsync using 2.6.4 client. Look at the various NEWS files at http://samba.anu.edu.au. It seems 2.6.0 has protocol 27. rsync-2.6.1 through 2.6.3 have protocol 28. rsync-2.6.4 has protocol 2.6.4.
correct, the rsync protocol # has been increasing with the last few releases i'm inclined to assume this is 'correct' behavior ...
I think also, but why don't you bump rsync to 2.6.4 also on x86? ;)
because there's some I/O timeout issues still ... search bugzilla for the open bugs
