similar to: small security-related rsync extension

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

I have been using delay() quite successfully to 'load on reference' some large data files (earthquake catalogues). One minor difficulty I have not been able to overcome is that upon first reference, the data set is loaded into memory as expected, but also remains as a permanent object in the user's environment, instead of appearing to be only in the library from which it was loaded.

--Multipart_Mon_Nov_24_14:51:09_1997-1 Content-Type: text/plain; charset=US-ASCII >>>>> "PaulG" == Paul Gilbert <pgilbert@bank-banque-canada.ca> writes: MM> The code is basically in V&R 1 and 2; V&R2 on p.167. I have it as a MM> C function that I used to dyn.load into S-plus in order MM> to prove that S-plus was using it.

In 0.65.0 lib.source() within library() works differently and fails to correctly "load" a library when it wants to change an object that it has defined previously: Below is a very short shar file that produces a "minimal" example [no attachment, just appended]. To reproduce {read on, before doing it!} do sh < libBug.shar <<<<< the file name you gave

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dear list members, there are two new rsync-features I made up and would like to discuss with you. If you think these new features might be useful for the whole rsync-community, please give me a note and I'll send you the patches (or post them here). 1.) Setting owner and/or group of backup files. In our servers I'm using rsync to backup

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

Please CC me directly as i'm not on the list. I have attached a patch against latest CVS (cvs diff -u) that adds the following functionality. I can break it up if you would prefer it in pieces. Comments welcome. o add compare-perms option This creates a new inode for a file even if only the perms have changed. This way if a file outside of destdir is hardlinked to a dentry inside

We use rsync to update an nfs server. After an update, we noticed that a large number of clients didn't see the updated data. It took me a while to be able to reliably reproduce this problem, but it happens on old and new versions of rysnc. It also happens across all the platforms we use here (sun/linux/netapp). This shows the problem: [Note my home directory is NFS mounted]

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

Hi, As far as I can tell, after version 2.6.4, the "--daemon" and "--temp-dir" options are not compatible anymore. Previous versions allow this. We use this heavily at my site. Is this an intentional change or bug? My command to start the daemon is this: /usr/local/bin/rsync --temp-dir=/.rsyncd-spool --daemon Thanks, -Eddie

In the past there's been a need to provide consistency between symbolic links or repository metadata during a sync. Currently, rsync renames files piecemeal. The attached patch (extremely ugly) attempts to resolve this by foregoing the rename step until the end. It adds a new option (if we didn't, ls might catch up). There are several issues to get over. The first big one in

Updated to current cvs without the --exclude-from - patch. This patch allows specifying a --link-dest path similar to --compare-dest except that unchanged files are hard-linked to the --link-dest path instead of producing a sparse tree. -- ________________________________________________________________ J.W. Schultz Pegasystems Technologies email address: jw@pegasys.ws Remember

In an effort to get my long-desired move-files functionality into rsync, I have created a version of my patch that runs as an extra pass at the end of the processing. This results in a simpler set of changes to rsync. I still think it would be nice to have incremental deletions during large transfers (as my first patch provides), but acceptance of this patch would relegate such quibbling to a

Hi, How about adding now option '--backup-only' that means making backups only and don't change any destination files? (I posted similar patch a month ago, but the patch was made for nightly snapshot of 20020808, which was tooo old! Laugh at me...) I want to use rsync with LVM snapshot to make incremental backups like below: 1) Make LVM snapshot of file system and mount it.

Martin, Just a minor fix. Jie, Try the -r option (or the --recurse) option instead. It looks like the source changed to this: options.c: {"recurse", 'r', POPT_ARG_NONE, &recurse}, But the help is still at: options.c: rprintf(F," -r, --recursive recurse into directories\n"); eric Jie Gao wrote: > > rsync: --recursive:

They seem to be for me, even when I don't pass in the --perms flag. This is a problem because I'm rsyncing to a samba mount with fixed permissions. Looking at rsync.c (for version 2.5.5) starting at line 204, I see this code snippet: #ifdef HAVE_CHMOD if (!S_ISLNK(st->st_mode)) { if (st->st_mode != file->mode) { updated = 1; if

Hi List, I had a need recently to efficiently synchronise between some large LUNs (boot drive disks) at two different datacentres. Solutions like drbd and $proprietary_array_vendors_software were overkill - we only needed (wanted!) to periodically synchronise these LUNs whenever major changes were generated on the source. On the other hand however, re-sending the entire disk contents each time

https://bugzilla.samba.org/show_bug.cgi?id=3653 Summary: Silence 'vanished files' messages Product: rsync Version: 2.6.8 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: count-samba@flatline.de

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.

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