similar to: Patch for 2.6.7 (affects --exclude used with --relative)

I'm not sure if I was relying on unspecified behavior, but I was in the habit of putting entries like this: /home/tug/public_html into an exclude file. This would omit everything under that directory. (I'm not sure if it omitted the directory itself, but I didn't care.) In rsync 2.6.7, this had no effect, and everything under /home/tug/public_html was copied. I notice that a new

I think you would implement it as a new type of filter rule. similar to 'P' (preserve) but with a timestamp or delta-time to define what counts as 'recent' as well as the pattern to match for this rule to apply (which could just be a wildcard matching anything by default, but could also use the full pattern-matching capabilities if required). Have a look at: the

I have been unable to figure out how to exclude directories that only exist on the source side when running rsync version 3.0.2 with --relative. Here is an artificial test that shows my problem in case 3). Any help would be appreciated. # mkdir -p /tmp/source/a/b /tmp/source/a/c # touch /tmp/source/a/b/hello /tmp/source/a/c/world 1) Try mirroring both b/ and c/, this works: # rsync -avn

Kudos all that maintain this awesome and enduring piece of software. Awesome job, many thanks. I’ve come across a use case that would greatly benefit form a —delete-older-than <secs> argument. This would behave the same as —delete only sparing files dest that have a creating time less than <secs> ago. How hard would this be to implement? Where would I start ? TIA, Francois

https://bugzilla.samba.org/show_bug.cgi?id=13112 Bug ID: 13112 Summary: receive_xattr heap overread with non null terminated name and xattr filter Product: rsync Version: 3.1.3 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 Component: core

Hello, I was trying to syncronize two directories with --include="*800*" or "800*" or "/800*", but I always et the same file list. Does option --include not outomaticaly exclude not matching files ? /usr/local/bin/rsync -n --include="800*" --rsh=remsh --rsync-path=/usr/local/bin/rsync -rzpogctS --log-format=%f /data/DWG/N/5225 plot1:/data/DWG/N building

Hi, I 'am trying to launch linux kernel 2.6.7 with initramfs. My pxelinux.cfg/default file looks as follows: default a1 prompt 1 timeout 600 label a1 kernel vmlinuz-2.6.7-1 append initrd=initramfs_data.cpio.gz root=/dev/ram0 init=/linuxrc Kernel image vmlinuz-2.6.7-1 and initramfs_data.cpio.gz was loaded succesfully by pxelinux. Kernel says: checking if image is initramfs... it is but

I'm trying to update my rsync on os x 10.4.5. downloaded the latest rsync-2.6.7.tar.gz as described in the configure --help I started ./configure and the output tells me that all works out fine. then running rsync (in /usr/local/bin) in bash the output still tells me, it would be: rsync version 2.6.0 protocol version 27 what am I doing wrong? thanks Simon

Thanks to recent achievements, rsync with the acl patch has been a viable alternative for cygwin environments as well. --- Excerpt from the man page source: (--acl | -A) option causes rsync to update the destination ACLs to be the same as the source ACLs. This nonstandard option only works if the remote rsync also supports it. Note also that an optimization of the ACL-sending protocol used by

https://bugzilla.samba.org/show_bug.cgi?id=3382 Summary: hang in read() in exclude.test of testsuite Product: rsync Version: 2.6.6 Platform: Alpha OS/Version: OSF/1 Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy:

I have released rsync version 2.6.7. You can read all about the latest improvements and bug-fixes that went into this release on this page: http://rsync.samba.org/ftp/rsync/NEWS The tar file of the source and its signature are here: http://rsync.samba.org/ftp/rsync/rsync-2.6.7.tar.gz http://rsync.samba.org/ftp/rsync/rsync-2.6.7.tar.gz.asc See the web site for other download

I have released rsync version 2.6.7. You can read all about the latest improvements and bug-fixes that went into this release on this page: http://rsync.samba.org/ftp/rsync/NEWS The tar file of the source and its signature are here: http://rsync.samba.org/ftp/rsync/rsync-2.6.7.tar.gz http://rsync.samba.org/ftp/rsync/rsync-2.6.7.tar.gz.asc See the web site for other download

I'd like to patch the generator hang bug recently fixed in my production environment, but it'd be nice to know if a 2.6.7 release is just around the corner. Do you have any kind of estimate on a release date Wayne? I don't care about specifics, but a general idea (a couple weeks, or a couple months) would help a lot in my decision making process.

https://bugzilla.samba.org/show_bug.cgi?id=3637 Summary: Regression 2.6.6 to 2.6.7 when syncing with 2.6.6 on windows - --no-r Product: rsync Version: 2.6.7 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org

There is no CONFIG_SCSI to enable in xenU. Is there any reason for this? I want to try out iSCSI and obviously it needs scsi support. Or would I be better doing it in dom0 and exporting it? thanks James

I have a small embedded 486 system that is having a very strange problem booting the linux kernel. The system boots fine normally, but if I don't do a proper shutdown on it (everything is in ramdisk anyway) then I can no longer boot the 2.6 kernel. It simply hangs after the "Ready.": SYSLINUX 2.10 2004-06-18 Copyright (C) 1994-2004 H. Peter Anvin boot: Loading

Hi, The patch below adds a "--ignore" option to rsync, which means "--exclude-but-dont-delete-even-if-we-specified--delete-excluded". I need this for a few tasks, the simplest of which is to have rsync resist trying to delete NetApp filers' ".snapshot" directories. The change is fairly simple (the boolean filter returns become tri-state), and works for me both

Hi, Given these C instructions: ============================== struct stru { struct stru *Next; }; struct list *NewStru = malloc ( sizeof ( struct stru ) ); struct list *tmp.3; ... tmp.3 = NewStru->Next; ============================== LLVM generates something like this: %tmp.0 = malloc %struct.stru ; <%struct.stru*> %tmp.3 = getelementptr %struct.stru* %tmp.0, int 0, uint 1 ;

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

I have question about multipath routing. I am running a 2.6.7 kernel (gentoo). I have a route with three nexthops on the same interface. I see a different nexthop being picked for different destination addresses. All is fine. Now if one of the nexthop goes down (arp entry times out and arp request doesnt get a response), does it remove the nexthop from contention and only use the remaining two