similar to: Trivial documentation patch

Hi! I am doing backups from a number of machines to an rsync server. For some time I was trying to come up with a solution, which would prevent users from peeking at each other's files, which are backed up. Finally, I've hacked rsync, introducing a new option "write only" for rsyncd.conf. When set to true, this option forbids the transfers from server to the client, thus solving

> Just curious: what about the rsync+ patch? Thanks for the reminder. I've just committed Jos's rsync+ patch onto the "branch_mbp_rsyncplus_merge" branch. If it works OK and nobody screams I will move it across onto the main tree tomorrow or Wednesday. I see the patch doesn't add documentation about the new options to the man page, so we should fix that in the future.

Here is a diff which should allow applying batch updates remotely ( as apposed to copying the batch files to the remote server and running rsync there ). Eg rsync --write-batch=test src dst1::dst rsync --read-batch=test dst2::dst Oli Dewdney diff -E -B -c -r rsync-2.5.6/flist.c rsync-2.5.6-remotebatch/flist.c *** rsync-2.5.6/flist.c Sat Jan 18 18:00:23 2003 ---

Hello everyone! I didn't find anything in the archives that seemed similar (same error, different offending lines of code). I'm having an issue with rsync on a couple of my servers. A couple of others run just fine but 2 of them give me the same message (see below) when I try to do backups from one server to these linux boxes. All of the linux boxes are the same and have the save

Hello! I am using rsync compiled with Cygwin on windows. I must call rsync from the *.bat script (I don't want to use a bash on Windows) and I have noticed that in the case when program compiled by Cygwin crashes via segmentation fault and default SIGSEGV handler is called, then it terminates process with exit status 0 as I see it from my *.bat script. (But if I invoke a program from bash

In case others find this of value, I wrote a patch to rsync 2.5.6 to give rsync in --daemon mode the ability to run a pre-transfer and post-transfer command. These options handle our need to prepare a server to receive files and to do some processing after receiving files. The options for /etc/rsyncd.conf are pretransfer script = /some/command/to/run posttransfer script =

https://bugzilla.samba.org/show_bug.cgi?id=2455 Summary: rsync --daemon segfaults if "log file = <file>" dir does not exist Product: rsync Version: 2.6.3 Platform: Sparc OS/Version: Solaris Status: NEW Severity: normal Priority: P3 Component: core AssignedTo:

Hello! In the attached file is patch for the option to set client connection limit. We had problem for dead hosts, so default system timeout is not enough. --conlimit option added Will be great to see this patch in the future version, so we do not need to patch every time. Thanks and Cheers, Eugene. -- -------------- next part -------------- diff -Naur rsync-2.6.8/errcode.h

Hi, One feature missing from rsync, and requested on this list before, is on-the-fly conversion of filename character encoding. For example, I often need to sync files having Hebrew filenames from a UTF-8 system (Linux) to an ISO8859-8 system (Cygwin on Windows 2000 using the non-Unicode Win32 interface). Other circumstances surely abound. Attached is a patch against rsync 2.6.2 that adds an

Hi, In http://sources.redhat.com/ml/cygwin/2002-09/msg01155.html, I noted that the often-observed hangs of rsync under Cygwin were assuaged by a call to msleep(). After upgrading my Cygwin environment to rsync 2.5.6, I'm seeing these hangs again, not surprisingly given a CVS entry for main.c notes that this kludge was not harmless: Revision 1.162 / (download) - annotate - [select for

https://bugzilla.samba.org/show_bug.cgi?id=13115 Bug ID: 13115 Summary: .yo sources incompatible with current yodl version Product: rsync Version: 3.1.2 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 Component: core Assignee: wayned at samba.org

I'm sure that someone's gonna complain that parsing the output is messed up by this patch, but then they should have told about the typo themselves :-) --- log.c.orig 2004-08-17 10:25:57.000000000 +0200 +++ log.c 2004-09-05 16:28:42.000000000 +0200 @@ -61,7 +61,7 @@ { RERR_WAITCHILD , "some error returned by waitpid()" }, { RERR_MALLOC , "error allocating core

Here a bug report about "!" not working properly in 2.6.4 and above, paraphrased... > Ok, see attachment. I've tested it right now between two hosts > running rsync 2.6.3-2 and 2.6.6-1. It works in the forward direction, > backwards it gives > > '!' rule has trailing characters: ! > rsync error: syntax or usage error (code 1) at

Using rsync 2.6.0 on both ends, I ran rsync -v --files-from files andrew@pimlott.net: . and got an error from the remote rsync. The reason is that the remote rsync is run as rsync --server --sender -vvR --files-from=- --from0 . which conflicts with a check in options.c that rsync must have two non-option arguments when --files-from is used. I tried again with the latest nightly

OK, I packaged up the current CVS as our first preview release for 2.6.0. You can grab it here: http://samba.org/ftp/rsync/preview/rsync-2.6.0pre1.tar.gz The MD5 checksum is: 70e9dea967f083c231b7821ef35aef1b rsync-2.6.0pre1.tar.gz There is not currently a .sig file for the package, but I'm looking into that next. Please test this and let me know if we have any remaining issues

This is a PoC patch for NFSv4/ZFS ACLs. The objective of the patch is that rsync --acls support NFSv4/ZFS ACLs without requiring a new command line option NFSv4 ACLs can't be represented using POSIX draft ACLs, if an NFSv4 ACL is present a separate POSIX draft ACL will not be present and there are new APIs to access NFSv4 ACLs. So we need to distinguish between NFSv4 ACLs and POSIX ACLs in

Some of the debug messages that rsync outputs (when verbose >= 2) can occur on both sides of the connection. This makes it hard to know which program is saying what. Some debug messages deal with this by outputting a "[PID]" string at the start of the message. Unfortunately, the startup message that tells us which pid is which is only output when verbose >= 3, so there's a

Hi. The small patch below fixes the building of 'mkrounding.o' when the build directory is outside the source directory. Art Haas Index: Makefile.in =================================================================== RCS file: /cvsroot/rsync/Makefile.in,v retrieving revision 1.128 diff -u -r1.128 Makefile.in --- Makefile.in 17 Dec 2006 00:40:18 -0000 1.128 +++ Makefile.in 27 Dec 2006

Hi everyone, I'd like to propose a patch for review. It enhances rsync when patched and compiled with slp support. It adds a new global boolean option, 'disable slp', which can be used to disable SLP advertisements at runtime. The idea behind this patch is to allow distributors to build rsync with SLP support compiled in, but to allow the users to turn it off without recompiling

Rsync-2.5.2 does not gracefully report connection and transfer errors and always properly return with a non-zero exit code, despite many assurances to the contrary in the code and commit logs. It seems a kludge to handle a special case of lost connections to older servers was FAR too aggressive! With '-vvv' I also print the source of the exit_cleanup() call, and optionally with