-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Suddenly I feel compelled to point out the existence of --temp-dir
On 10/26/11 22:52, Alex Jurkiewicz wrote:
> On Thu, Oct 27, 2011 at 5:30 AM, Wayne Davison wrote:
>> Here's a patch that should handle the above idea:
>> http://pastebin.com/UTbtFu8T
On Thu, Oct 27, 2011 at 5:30 AM, Wayne Davison wrote:
> Here's a patch that should handle the above idea:
> http://pastebin.com/UTbtFu8Ta
Unknown Paste ID!
Regardless, all your suggested changes still improve the capability of
rsync to run simultaneously on the same tree, so it sounds good. My
Hello,
It seems that the issue is todo with the network. However, I would suggest you
try with a different computer system to be sure. Additional notes follow :
--
> server: iperf -s -D -p 873
> (problematic network) client: iperf -c iperf.server.com -L 873
>
>
On Wed, Oct 19, 2011 at 9:59 PM, Alex Jurkiewicz wrote:
> These two patches change how rsync handles temporary files on the receiver
> side. The first patch adds a static token to rsync's temporary filenames.
> The second patch ignores files with this token when using --cvs-ignore.
>
[Sorry for
Thanks for the response..
>Is your output on this problematic network similar to the following :
>$ telnet mirrors.usc.edu 873
>Trying 68.181.195.4...
>Connected to hpc-mirror.usc.edu.
>Escape character is '^]'.
>@RSYNCD: 30.0
Yes, this is exactly the output.
>Also, what happens if you add -n (--
On 10/26/2011 12:39 AM, Alex Jurkiewicz wrote:
Any comments?
On Thu, Oct 20, 2011 at 3:59 PM, Alex Jurkiewicz wrote:
Hi all,
These two patches change how rsync handles temporary files on the receiver
side. The first patch adds a static token to rsync's temporary filenames.
The second patch ign
Hello,
Is your output on this problematic network similar to the following :
$ telnet mirrors.usc.edu 873
Trying 68.181.195.4...
Connected to hpc-mirror.usc.edu.
Escape character is '^]'.
@RSYNCD: 30.0
Also, what happens if you add -n (--dry-run) to the following command :
> rsync -artv rsync:/
