similar to: --delete and --dirs

I know that there are a million messages from newbies who cannot get --delete to work. This message is special. :) --delete works fine for me EXCEPT when the following two conditions are present: 1) I am using the --relative option, and 2) the deleted file is in a subdirectory of the SRC directory. Here is a demonstration of how to recreate this bug: lenny@mythtv:/tmp$ rsync --version rsync

https://bugzilla.samba.org/show_bug.cgi?id=12367 Bug ID: 12367 Summary: temporary lines in --progress output are not cleared Product: rsync Version: 3.1.2 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 Component: core Assignee: wayned at samba.org

As those of you who watch CVS will be aware Wayne has been making progress in reducing memory requirements of rsync. Much of what he has done has been the product of discussions between he and myself that started a month ago with John Van Essen. Most recently Wayne has changed how the file_struct and its associated data are allocated, eliminating the string areas. Most of these changes have been

I have a model class in rails that has a class variable that is a ferret index. For some reason, the methods in my class that refer to the class variable are getting lock conflicts. Can anybody see any obvious reason why? I notice that it keeps leaving a lock file in the index directory. I thought auto_flush was supposed to remove the lock automatically after every operation. Is there

I have a script that does a weekly backup on a local backup harddrive with the following command: # rsync -aRxW --delete / /mnt/backup Today I got errors because the target drive was full. It appeared nothing on the targed drive ever got deleted. When I used the following command to backup only my home dir, it worked as it should. # rsync -aRxW --delete /home/joost /mnt/backup Using rsync

Hi to all the people (again), I'm doing some simulations with the memisc package of an own function, but I've the problem that I didn't know how to read the result of such simulations. My function is: > Torre<-function(a1,N1,a2,N2) + {Etorre<-(a1*N1)/(1+a1*N1) + Efuera<-(a2*N2)/(1+a2*N2) + if(Etorre>Efuera)Subir=TRUE + if (Etorre<Efuera)Subir=FALSE +

We've just been hit rather badly by a very nasty bug that can cause rsync to silently discard files or fill them with zeroes. It happens when e.g. opendir() succeeds but readdir() returns an error; rsync does not check for an error from readdir() and so simply ignores the error (along with any remaining files in the directory). No error is reported to the user, who will then happily

Hi. Here's a patch for copying the atimes of files when -t/--times is given. I bumped the protocol to 29 since it sends more data over the wire. It obviously does not send the atime if it's sending data to an older rsync version. It passes all the tests (including the added atime.test) for me on a: Linux Debian/3.0 gcc 2.95.4 (debian), glibc 2.2.5 system. Any questions/feedback? I

I got numerous warnings when building rsync on IA64 (Itanium-2) using Intel C/C++ compiler (see attached). Is this expected? Thanks, Michael -------------- next part -------------- Script started on Fri 21 Sep 2007 06:14:05 PM BST ~/src$ ls -alt total 222884 -rw-r--r-- 1 mccssmb2 mcc101 0 Sep 21 18:14 build_rsync drwxr-xr-x 8 mccssmb2 mcc101 4096 Sep 21 18:14 . -rw-r--r-- 1

This is a patch to add an --rsync-exclude option to rsync-2.5.6cvs. File names in .rsync- (or .rsync+) are excluded (or included) from the file lists associated with the current directory and all of its subdirectories. This has advantages over --cvs-exclude for backing up large file systems since the .cvsignore files only apply to the current directory: unless the .cvsignore restrictions apply

https://bugzilla.samba.org/show_bug.cgi?id=3825 Summary: rsync won't delete directory with excluded files Product: rsync Version: 2.6.8 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: vanes002@umn.edu

I posted a patch a few days ago that adds copying of atime. At that time, it was just enabled with -t/--times. After some time, we have figured out that that choice might not have been the best. Here's a new version of the patch (relative to CVS) that adds -A/--copy-atime instead. It also includes a test case. Any feedback on this patch and/or the previous one that I posted?

Hi, first of all, sorry for taking so long. Unfortunately, some other tasks kept coming up. Anyway, attached is the version of the flags patch, that is based on the one I'm using with 2.6.9. It is against the rsync-3.0.0pre9 release. I've included the option name change from the repository, so the option is now called --fileflags. Improved from the previously distributed version is the

OK, I searched through the archives and didn't find anything so I must be doing something stupid. I just compiled 2.6.3 and am trying to get it to run on linux 2.6.8.1 kernel with a more or less fedora core2 environment. I was trying between two systems but I have narrowed it down to what I believe is a pretty simple case. Here is my setup/test: Last login: Mon Oct 4 19:30:49 2004

> 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.