On 5/25/2010 6:41 AM, Mag Gam wrote:
I know rsync can do many things but I was wondering if anyone is using
it for data deduplication on a large filesystem. I have a filesystem
which is about 2TB and I want to make sure I don't have the same data
in a different place of a filesystem. Is there an
On 4/24/2010 8:30 AM, Michael wrote:
I have a little problem to get my include / exclude working:
I want to sync /etc /home and /usr/local (and all files/dirs beneath)
to REMOTEHOST:/dest
There are some huge files in /home which I want to exclued
I have set up an include/exclude file but I
Paul Haas wrote:
On Sun, 3 Apr 2005, Wayne Davison wrote:
On Mon, Apr 04, 2005 at 07:28:02AM +0200, Joost van den Broek wrote:
When you just give an empty rsync command, it should also exit with an
exit code (1). But the errorlevel gets set to no. 256 instead.
As mentioned in the other message
Joost van den Broek wrote:
I can confirm too that this has solved the problem for me. It's time for a new
cwRsync release :)
- Joost
If Tev is going to release a new cwRsync, I might ask that he adds the
patch Wayne made for the problem I experienced with multiplexing
errors. This appears
Benjamin Watkins wrote:
I will let you know how the patch works for me. I am currently
running it from Workstation 1 to Server 1.
After more extensive testing with this patch, I can confirm that it does
indeed resolve this issue for me under Cygwin.
If Tev repackages his cwRsync package, I
Benjamin Watkins wrote:
Benjamin Watkins wrote:
So far this observation has been made on one out of one clients that
I have tested. I was able to repeat this error several times on this
machine before I discovered the message in the server log pointing me
to the long file name problem. I am
Wayne Davison wrote:
On Fri, Apr 01, 2005 at 03:54:38PM -0500, Benjamin Watkins wrote:
multiplexing overflow 1:296 [sender]
This indicates that there is an error message arriving (1) that has a
length of 296 bytes, but this is too long for the line buffer in
readfd_unbuffered(). I changed
I installed the newly released version of cwRsync today on a few Windows
machines and have noticed a new problem that I have not seen mentioned
anywhere.
When syncing to an NT machine used for backups, my rsync client exited
at the end of the transfer with the following message to standard
Benjamin Watkins wrote:
So far this observation has been made on one out of one clients that I
have tested. I was able to repeat this error several times on this
machine before I discovered the message in the server log pointing me
to the long file name problem. I am running a test from
