similar to: am I missing something, or are permissions always preserved?

Hello, i'm using rsync 2.6.0 for daily-syncing some remote AIX 5.2 machine to a local linux (RH 7.3) with using the --link-dest option for saving space on incremental backups. Even if there are no changes on the AIX machine, all files are newly transferred on every new sync. My test scenario (actisi=remote aix machine, actisa=local linux machine): =====> Initial rsync [mma@actisa

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

As I reported a while back rsync doesn't handle metadata (permissions and ownership) in dryrun mode. I offered to make a patch and that offer still stands. I didn't have the time for it until now and want to pick it up again. I had some ugly hack back then but I want to redo it in a clean way. I would like some input on my thoughts. IMHO, it would be ideally if the check for dry_run

Hiya, I can see it's a regular subject on this list. I, like others wanted to use rsync to synchronise two block devices (as it happens one lvm volume and one nbd device served by qemu-img on a remote host from a qcow2 disk image so that I can keep the old versions) As I couldn't find any report of it being done successfully, I'm just sharing my findings as it might benefit others.

https://bugzilla.samba.org/show_bug.cgi?id=1764 Summary: dry-run does not show changes in owner / group, permission, or timestamp Product: rsync Version: 2.6.3 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org

Our environment: samba4 (alpha12) running on centos 5.4. We are experimenting with Hyper-V 2008 R2 Failover Clustering, which requires Active Directory. We are trying to see if samba-4 will work as the AD server. We are trying to create 2 node failover cluster. Both nodes have joined the domain successfully (with samba-4 as the DC). But subsequent steps of creating the "Failover

The attached patch adds an option --drop-suid which caused rsync to drop setuid/setgid permissions from the destination files. ie, even if the source file is setuid, the target file will not be. Added as we want to rsync the same files to machines both inside and outside our firewalls. For machines inside the firewall some files should be suid, for machines outside the firewalls they should

Hi Guys, We are trying to come up with Bi-Endian(neutral endiness) compiler using the LLVM. For a introduction . http://www.drdobbs.com/architecture-and-design/writing-a-bi-endian-compiler/240003090 Did someone from the group ,aware of such project . Thank you ~Umesh

Hi, Recently, there have been some fundamental achievements regarding acl-support on the cygwin platform. I thought that it would be convenient to offer an acl-patch enabled rsync as a part of the cwrsync package (a yet another minimalist rsync on cygwin solution). I get some compilation errors. What I did: - Downloaded acl patch v1.113 from rsync site - Run commands below In the rsync source

This appears to be a feature :-) I'm running rsync 2.5.5 on Solaris 8, and testing transferring files between two boxes with permission preservation turned *off*. I have three files: 700 with permissions 700 770 with permissions 770 777 with permissions 770 The umask for the target system is set to: 007 [I have checked this via prints from the rsync code] When the files get transferred,

Hi -- I was very keen to download rsync and give it a whirl with the new --link-dest feature. However, I was terribly puzzled when I couldn't seem to get it working, even though --compare-dest with the same argument would work. It seemed like new files would be transferred even though files existed in the compare-dest/link-dest location; compare-dest would detect them but link-dest would

I have discovered that rsync 2.5.6 uses the mkstemp() routine wich do not have a 64bits version into the AIX libc. A very simple workaround to the big files writing rsync pb. is to not use this routine that create files w/ mkstemp() by modifying the "syscall.c" source file at line 154 as following : #if defined(HAVE_SECURE_MKSTEMP) && defined(HAVE_FCHMOD) become #if

(I'm not subscribed; Mail-Followup-To set.) Contrary to the claim in the output of ./configure --help, $CPPFLAGS is in fact not influential. --- rsync-2.5.5/Makefile.in~ 2002-03-24 23:36:34.000000000 -0500 +++ rsync-2.5.5/Makefile.in 2002-11-12 17:52:04.000000000 -0500 @@ -9,6 +9,7 @@ LIBS=@LIBS@ CC=@CC@ CFLAGS=@CFLAGS@ +CPPFLAGS=@CPPFLAGS@ LDFLAGS=@LDFLAGS@

Hi, I'm running rsync 2.5.6. I use it to backup a RH 7.3 file server (samba+appletalk) to a FAT32 external HD. I get the following output: .1e6prS failed: Invalid argumentsp_ind/Emails ind/.Icon .fJ98aa failed: Invalid argumentsp_ud/Emails ud/.Icon .qLRVCT failed: Invalid argumentkt/02_Tegninger/planer/ai/.Icon .zM65uw failed: Invalid argumentkt/02_Tegninger/planer/fmz/.Icon mkstemp

I'd like to suggest that this is now a great time to create two separate cvs branches for the rsync product. One, which I'll tentatively call 2_5, would hold the version of the code that has been released to the world as 2.5.6. The other, which I'll tentatively call head, would hold the development activity leading up to the next field release. I'm not bound to these names, but I

Under Aix directories have the mode 024xxxx instead of the customary 04xxxx. Because of this when you sync a directory to or from an Aix system it's never up to date. Here is a patch which fixes this. It causes rsync to look at only the bits that chmod actually influences, 07777, when deciding whether or not the modes differ. I was surprised there wasn't an existing constant for 07777,

This is a patch to control unix permissions when uploading to a rsyncd-server by setting rsyncd.conf options. cu, Stefan -- Stefan Nehlsen | ParlaNet Administration | sn@parlanet.de | +49 431 988-1260 -------------- next part -------------- diff -ur rsync-2.5.5/loadparm.c rsync-2.5.5-umask/loadparm.c --- rsync-2.5.5/loadparm.c Mon Mar 25 05:04:23 2002 +++ rsync-2.5.5-umask/loadparm.c Sun Mar 2

On Fri, Jul 31, 2015 at 12:15 AM, Herbie Robinson <HerbieRobinson at verizon.net> wrote: > I have been quietly working on a port of LLVM to Stratus VOS. The OS is > always big endian (because customers need to migrate data to new hardware > quickly and can't afford to convert). This entails presenting a big endian > programming model no matter what the hardware does. We

Sviatoslav Sviridov [mailto:svd@ns1.lintec.minsk.by] wrote: >It would be good if attached patch will be included in upstream. This >patch adds option --apt-support for rsync and with this option rsync >will print some additional information about file being transfered. No >program logic changed. Having this option in rsync we can have apt with >rsync method support. 1. What is apt?

Hi, i finished my storage compression patch for rsync. WARNING - THIS IS ONLY FOR TESTING! How does this work? Just add a "-Z" option to your common rsync commandline parameters. The destination files will be stored in a compressed way (by using a hardwired call of gzip). This works in both directions: rsync -Z -av mydir user@remote:/dir and rsync -Z -av user@remote:/dir