similar to: minor typo fix for 2.6.3 pre 1

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

Greetings. I'm not sure if this is the place or not, but I wanted to pass on this patch (against CVS as of today) to document two exit values that are used by rsync but not yet in the docs. Please let me know if there's a better place to send it. Many thanks to the developers and maintainers of rsync for all the excellent work! Jon Index: rsync.yo

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

https://bugzilla.samba.org/show_bug.cgi?id=9416 Summary: --files-from : RERR_PARTIAL vs RERR_VANISHED Product: rsync Version: 3.1.0 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: penning at uu.nl

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 =

All, I am using rsync to backup a list of files that are in use by an application. Files can be deleted, created, or modified by the application whilst rsync is running. I am getting the following output line, in amongst lots of succesful transfers, when running rsync, : send_files failed to open //ca/spool/smdiq/005.973416/9734161182.1: No such file or directory This then results in an RC of

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

Hello, I like to use rsync to transfer over mine and other peoples ever changing mail folder onto a remote server. My Server (FreeBSD 5.4) RSYNC Version is: 2.6.6 Protocol Version 29 My Client (OSX 10.4.2) RSYNC Version is: 2.6.3 Protocol Version 28 I use this command rsync -vvv --progress --stats --recursive --times \ --perms --links \ --delete /test/my?email?folder/*

All, During development of a backup solution with rsync I experienced some failed backups because of RC 23, partial transfer. These were because the application using the data I was backing up, was still active, and had deleted a file inbetween rsync compiling the file list and then transfering the file. After some feedback from Wayne Davidson and JW Schultz suggesting the solution to this,

Hello all, long first post, sorry. I've been using rsync in a backup script for several years now. The script has been stable, and the backup system as a whole pretty much error free for at least 2 years, the only hiccups being minor tweaks to accommodate changes to base utilities used (lvm, namely). In broad strokes, here is what happens for the home directory on my notebook(s). 0.

Greetings, Upon a suggestion to improve the --timelimit patch, I have also added a --stopat option. You can get the patch from this URL and/or cut/paste it from below. http://www.terry.uga.edu/~jft/rsync-timelimit-stopat.patch.gz Here are the details... --timelimit=T This option allows you to specify the maximum number of minutes rsync will run for. This time starts when

Greetings, I have written a patch for rsync-2.6.1pre-2 which adds a --time-limit=T option. When this option is used rsync will stop after T minutes and exit. I think this option is useful when rsyncing a large amount of data during the night (non-busy hours), and then stopping when it is time for people to start using the network, during the day (busy hours). If this patch is accepted it may

Hi, I spent a little bit of time trying to debug a segfault in rsync 2.5.0, and after discovering it was in loadparm.c, I noticed that the bug had been worked around in the current CVS by removing a free() statement. That fix seems less than optimal; here's a patch which should fix the memory leak. -------------- next part -------------- --- loadparm.c.~1.40.~ Sun Dec 2 03:16:15 2001 +++

Hi all, While trying to mirror a filesystem from one machine to another (for backup purposes) I get the following error: [root@samantha root]# /usr/bin/rsync -qavxzC --delete chandler:/var/ /bigdisk/backup/chandler/dev-md5-var/ root@chandler's password: rsync error: unexplained error (code 24) at main.c(1045) Does this mean anything to anybody? Regards, Graham --

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

I have released rsync 2.6.3pre2 -- the second (and final) pre-release version of 2.6.3. Please help out with the testing so that the code gets a good workout before 2.6.3 is released. (Note that this version will not be in testing for as long as 2.6.3pre1 was -- I'd like to get it released in a week or two, if possible.) To see what has changed since 2.6.2, read this text file:

I have released rsync 2.6.3pre2 -- the second (and final) pre-release version of 2.6.3. Please help out with the testing so that the code gets a good workout before 2.6.3 is released. (Note that this version will not be in testing for as long as 2.6.3pre1 was -- I'd like to get it released in a week or two, if possible.) To see what has changed since 2.6.2, read this text file:

Hello Rsync users, I,m using rsnapshot, an incremental backup too based on rsync to backup data from remote servers using ssh. The data mainly consists of windows shares (samba & windows NT4 Server). Most of the shares backup ok but when backing up some shares the following error is recorded in /var/log/rsnapshot : [20/Mar/2004:01:17:45] ERROR: /usr/local/bin/rsync returned 23 Once this

A new 2.6.0 feature is supposed to use a different exit code when the only 'errors' were from files that disappeared between the building of the file list and the actual transfer of files. But if the client is local and the server is remote, IOERR_VANISHED gets set on the remote server, but is never passed to the local client (the io_error value is passed at the end of the file list, not