From cc32ffe05f5b8453ac09f2a12b2a17e41d9d7584 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Thu, 30 Jul 2015 13:29:45 -0400 Subject: Fix rsync special remote to work when -Jn is used for concurrent uploads. --- .../comment_1_793bbc86b495dda0328c35cb5abe4fad._comment | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 doc/bugs/rsync_remote_with_-J2_fails/comment_1_793bbc86b495dda0328c35cb5abe4fad._comment (limited to 'doc/bugs/rsync_remote_with_-J2_fails') diff --git a/doc/bugs/rsync_remote_with_-J2_fails/comment_1_793bbc86b495dda0328c35cb5abe4fad._comment b/doc/bugs/rsync_remote_with_-J2_fails/comment_1_793bbc86b495dda0328c35cb5abe4fad._comment new file mode 100644 index 000000000..eeb4b34af --- /dev/null +++ b/doc/bugs/rsync_remote_with_-J2_fails/comment_1_793bbc86b495dda0328c35cb5abe4fad._comment @@ -0,0 +1,13 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2015-07-30T17:18:24Z" + content=""" +The -J1 is a red herring; there's no progress output for -J modes, so the +whole transfer runs quietly there. + +The -J2 failure is because the rsync special remote implementation uses a +local scratch directory which is supposed to be empty. But, since it uses +the pid of the process to create the directory name, concurrently transfers +will use the same scratch directory and so interfere with one-another. +"""]] -- cgit v1.2.3