similar to: [Bug 8268] New: Wrong unchanged_attrs test for symlink ownership

Similar to --omit-{dir,link}-times: --omit-device-times omit device files from --times --omit-special-times omit sockets and fifos from --times Also, fix corner case that allows --omit-dir-times to be ignored. See unchanged_attrs() and recv_generator()'s call to try_dests_non(). Marc. diff -aNpRruz -X /etc/diff.excludes rsync-3.2.7/generator.c devel-3.2.7/generator.c ---

https://bugzilla.samba.org/show_bug.cgi?id=7622 Summary: Factor out common logic from itemize and unchanged_attrs functions Product: rsync Version: 3.1.0 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P3 Component: core AssignedTo: wayned at samba.org

Hi, below you find a patch fixing a bug in the file comparison code: The current code skips the unchanged_file() check when that check succeeded for an earlier candidate, which could lead to accepting a file with a different checksum as unchanged, for example. Please be aware that the patch is untested. Florian diff --git a/generator.c b/generator.c index a112da6..2df1b28 100644 ---

I noticed that rsync itemizes "p" whenever it copies a new file and finds an alternate basis file whose permissions differ from those to be applied to the destination file, even when --perms and --executability are both off. To see this, run the following in an empty directory: mkdir src dest basis touch src/file basis/file chmod 600 src/file chmod 644 basis/file rsync -r -ii

https://bugzilla.samba.org/show_bug.cgi?id=4561 ------- Comment #1 from matt@mattmccutchen.net 2007-11-04 14:51 CST ------- Created an attachment (id=2960) --> (https://bugzilla.samba.org/attachment.cgi?id=2960&action=view) Implementation of --tweak options Here, finally, is an implementation of the --tweak options! Now that bug 5051 and the omission of mtimes from unchanged_attrs

Skipped content of type multipart/alternative-------------- next part -------------- diff -urN rsync-3.0.2-orig/generator.c rsync-3.0.2/generator.c --- rsync-3.0.2-orig/generator.c 2008-03-28 10:30:11.000000000 -0700 +++ rsync-3.0.2/generator.c 2008-05-07 15:35:08.317364774 -0700 @@ -1508,6 +1508,7 @@ if (preserve_links && S_ISLNK(file->mode)) { #ifdef SUPPORT_LINKS + int iflags =

https://bugzilla.samba.org/show_bug.cgi?id=7110 Summary: Symlink fake-super data is silently lost when sys_lsetxattr fails with EPERM Product: rsync Version: 3.1.0 Platform: All OS/Version: All Status: NEW Severity: major Priority: P3 Component: core AssignedTo: wayned at

https://bugzilla.samba.org/show_bug.cgi?id=5644 Summary: Option to recheck basis dirs for existing dest files Product: rsync Version: 3.1.0 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy:

https://bugzilla.samba.org/show_bug.cgi?id=8073 Summary: Regress: 3.0.8 cannot compile on freebsd Product: rsync Version: 3.0.8 Platform: x86 OS/Version: FreeBSD Status: NEW Severity: blocker Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: grarpamp at gmail.com

A while ago (2.6.2), I built and posted a patch which caused rsync to "do the right thing" where --link-dest was being used and where files had been changed only in their ACLs. I've recreated this for 2.6.8 (there were some small differences). I've tested this using --link-dest copying from Linux-Linux and Linux-Solaris. I plan to test Solaris-Solaris too, of course. But

Fix config file parsing for VMX domains. If we define "vif" in the config file, image.py will raise error "vmx: missing vbd configuration". The reason is "vif" is dealt with as a "vbd" device. This patch fixes this issue by dealing with "vbd" and "vif " separately, removing "macaddr" arg and parsing mac address from

Hi, i had the problem, if i migrate a domU to another Dom0, i have to copy the sxp file tool (and the same problem in a few other scenarios too). For an easier solution, i created a tool to generate a domU-sxp-file from/for a running DomU. If anyone need it too, it is available here (compiled for amd64): http://www.xncore.com/download/stuff/xntool-running2sxp.gz Usage: xntool-running2sxp

# HG changeset patch # User Lutz.Dube # Node ID ca2c8c262dbaa6b2521cec60af7cd688dabdf850 # Parent 8992134dcfd0b9e1e86f4111e68a8aa48bd33c3c Values of cpu_weight and cpu_cap are lost after xend restart For managed domains in state ''halted'' I always get default values for cpu_cap / cpu_weight after xend restart. This is because the names of parameters differ between a SXP file to

Comparing my last know working configuration with the current one, it appears to be gagging on the new localhost\.localdomain that is in the configuration file. I don''t know if this got added by my machine when compiling. diff -ur xen-3.0-testing.hg/install/etc/xen/xend-config.sxp xen-unstable.hg/install/etc/xen/xend-config.sxp --- xen-3.0-testing.hg/install/etc/xen/xend-config.sxp

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

Package: xen-utils-common Version: 4.4.1-9 Severity: important This bug was already reported as #763102 and was brushed off because maintainer says it implicates xend which is not there in 4.4 anymore. However, this problem is present during upgrade from wheezy to jessie and means that reboots are not possible without physical interventions. As noted in #763102, during shutdown, we can see this

> On Sat, Apr 16, 2016 at 5:40 PM, rgritzo <rgritzo at gmail.com <https://lists.centos.org/mailman/listinfo/centos-virt>> wrote: > > so i guess i was not paying too close attention and upgraded to xen 4.6.1 before i migrated my domU configurations to libxl :{ > > Just FYI, as a fall-back you can always move yourself to the Xen 4.4 "track" by: > 1.

Package: xen-utils-common Version: 4.0.0-1 Severity: normal I am also struggling with this. I got farther by creating a .sxp file (xmexample.hvm.cfg is from /usr/share/doc/xen-utils-common/examples): # xm create -n -f xmexample.hvm.cfg | tail -n +2 > xmexample.hvm.sxp (why xm create -n mixes diagnostics with the output of -n on stdout, I do not know) and then specifying it on the command

On one of my xen hosts a virtual machine does not start at boot. I can see that xendomains gives an error: service xendomains start Starting auto Xen domains: fszeleNo handlers could be found for logger "xend" Error: Disk isn't accessible No handlers could be found for logger "xend" Error: Disk isn't accessible An error occured while creating domain fszele: Usage: xm

Working with rsync 3.0.2, it appears that rsync isn't unlocking files before setting the file attributes when those files already exist. This generates error messages on subsequent such as: rsync: rsync_xal_set: lsetxattr("locked_file","test_xattr") failed: Operation not permitted (1) rsync: rsync_xal_clear: