On Mon, 2009-06-08 at 11:01 +0530, Jignesh Shah wrote:
You are correct Carlos but it wasn't happening with rsync-2.6 and
started happening with rsync-3.0.6. Do you have any idea on this?
The could not make way error message is new in rsync 3.0.0 (see
On Wed, Jun 3, 2009 at 3:42 PM, Leen Besselinkl...@consolejunky.net wrote:
For people who don't know what it does, it implements backup of open files on
Windows with rsync.
snip
My hope is to get something that works so well to have it included it in the
cwrsync-installer:
On Thu, Jun 4, 2009 at 12:09 AM, Daniel.Lidaniel...@usish.com wrote:
I think multi-client can improve performance, but limit is the same as
above.
I don't think I understand! Can I start more than one rsync --daemon
instances then?
What kind of performance you are concerning,
Ryan Malayter wrote:
On Wed, Jun 3, 2009 at 3:42 PM, Leen Besselinkl...@consolejunky.net wrote:
For people who don't know what it does, it implements backup of open files
on Windows with rsync.
snip
My hope is to get something that works so well to have it included it in the
Rahul Nabar wrote:
On Thu, Jun 4, 2009 at 12:09 AM, Daniel.Lidaniel...@usish.com wrote:
I think multi-client can improve performance, but limit is the same as
above.
I don't think I understand! Can I start more than one rsync --daemon
instances then?
What kind of performance you are
On Mon, Jun 8, 2009 at 2:55 PM, Leen Besselinkl...@consolejunky.net wrote:
I think Daniel was trying to say, cpu might not be the bottleneck, it could
be network or something else (I doubt it's memory rsync 3 pretty much solved
that for most) and if you ask me it's probably disk.
Ah! I see.
On Mon, 2009-06-08 at 22:39 -0500, Rahul Nabar wrote:
If you're not using different partitions on different disks, then
doing
anything in parallel is probably going to slow it down
(reading/writing
all over the disk, means more seektime, which means waiting).
No, its just a single
