On Mon, Feb 22, 2010 at 10:53 AM, Javier Henderson jav...@kjsl.org wrote:
(Client) Protocol versions: remote=29, negotiated=29
Invalid flist flag: 1004
I looked at both 2.6.8 and 2.6.9 last week and didn't see any way for the
old code to construct a 0x1004 value for the file list flags, but
On Tue, Feb 23, 2010 at 12:55 PM, Eliot Moss m...@cs.umass.edu wrote:
The latest rsync (3.0.7-1) under an up-to-date cygwin
on Windows 7 x64 gets into some kind of busy wait
situation when transferring large files over ssh.
rsync, ssh, and zip can all be consuming much cpu time.
[...] I
On Wed, Feb 24, 2010 at 2:59 PM, Felipe Alvarez felipe.alva...@gmail.comwrote:
A large file (2+ GB) needs to be transfered, but I see more than one
temp file for it.
If you're using 2.6.8, upgrade to a newer version -- it has a bug where an
interrupted transfer could leave a temp file lying
[Going through old email. I wanted to confirm whether there was an
rsync bug here.]
On Wed, 2010-02-03 at 18:16 -0500, Ryan Flannery wrote:
The command I'm using is this:
rsync -avz --delete --delete-excluded --exclude-from=foo.txt /etc/
$dest:path
Where foo.txt contains either:
Is there any parameter in the rsync binary that I can finish the time the
binary should wait to start a file transfer, otherwise close the rsync
binary. As I read the timeout is a parameter used when the connection has
already been established, and when it is not, which parameter I can use?
--
Eduardo Terzella (eterze...@gmail.com) wrote on 6 March 2010 21:05:
Is there any parameter in the rsync binary that I can finish the time the
binary should wait to start a file transfer, otherwise close the rsync
binary. As I read the timeout is a parameter used when the connection has
already
