similar to: rsync - using a --files-from list to cut out scanning. How to handle deletions? (fwd)B

Folks, Thinking again about the issue of changed attributes for a file in source that is identical in content to a file in destination that is hard linked get propagated to the --link-dest directories I would like to suggest a new flag, (perhaps called something like --preserve-linked-attributes), to allow callers to get the behaviour that is needed to allow the use of recycled

Kevin, Thanks for your response. Some observations are inter-lined below. Rob. Regards Rob. Bell e-mail: Robert.Bell at csiro.au -- Dr Robert C. Bell, BSc (Hons) PhD Technical Services Manager Advanced Scientific Computing CSIRO IM&T Phone: +61 3 9669 8102 | Mobile: +61 428 108 333 | CSIRO 93 3810 Robert.Bell at csiro.au | http://www.csiro.au/ | http://www.hpsc.csiro.au/

Folks, We use rsync extensively for protecting data by making backups. Thank you to the authors and maintainers. Like many others, we use the --link-dest option to cut down on the space occupied by the backups. Unlike many others, we re-cycle old backup directories. Since most file systems change only slowly (ours average about 0.5% of files and about 1.5% of data being churned each day), a

Wayne, Thanks for the information - that looks useful for the future, and would replace our option. Rob. > Date: Fri, 24 Aug 2012 23:10:43 -0700 > From: Wayne Davison <wayned at samba.org> > To: Robert Bell <Robert.Bell at csiro.au> > Cc: rsync at lists.samba.org > Subject: Re: [patch] link-dest messages and max-size warnings (fwd) > > On Thu, Aug 23, 2012 at

Folks, bugs at stupidkitties.com wrote: " I was wondering if it'd be feasible to add an option (or multiple options, depending on the desired granularity) to cause rsync to treat changes in file attributes the same way it treats changes to the file's contents when it encounters hard links at the destination. Maybe something like --relink-p or something?" One of colleagues has

rsync watchers, I've been using rsync version 3.1.1+, and do like the improved --stats output: e.g. Number of files: 2480403 (reg: 2034290, dir: 233487, link: 212174, special: 452) Number of created files: 356 (reg: 6, dir: 3, link: 347) Number of regular files transferred: 16 ... - thanks to the developers. However, I want to be able to look at the --stats output and make a decision

rsync Folks, The following explanatory text is by me and the patches are by Rowan McKenzie for use by the Advanced Scientific Computing group at CSIRO. This patch builds upon the --link-dest patch by Bryant Hansen (Thanks heaps!). 1. The original patch provided an alternate behaviour for rsync when using the --link-dest option. When there are identical files in the source and link-dest areas,

+1 to that idea. Ask the same couple month before during migration from 1.x to 2.x but got no answer from someone who able to change this. On Tue, 17 Nov 2015 10:35:11 +0200 Teodor Milkov <tm at del.bg> wrote: > Hello, > > Currently doveadm tool can't be used with read-only source locations > because it's trying to create lock files. > > I'd guess lock

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

Hello, Currently doveadm tool can't be used with read-only source locations because it's trying to create lock files. I'd guess lock files shouldn't be necessary on a read-only media, because no one else is going to change anything while our doveadm instance is running anyway. Example: doveadm import -u test at example.com

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 =

Dear rsync folks, Re the recent discussion of: Subject: RE: Does files-from work with --delete? We have come across the same issue, in doing partial backups of a file system and using the --files-from and --link-dest feature to a re-cycled area. Files that should be deleted tend to build up. I mentioned this issue to a colleague. He suggested that after the backup is done, a reverse rsync -n

Way back: > > ---------- Forwarded message ---------- Date: Mon, 2 Jun 2003 > > 09:56:50 -0700 (PDT) From: Michael Rubel <mrubel at > > galcit.caltech.edu> To: rsync at lists.samba.org Subject: > > --link-dest when target and compare_dir both have file > > > > Hi J.W. et al, > > > > Kevin Everets was kind enough to inform me about some

On Wed, Oct 03, 2018 at 03:47:11PM +0300, Berindeie Avram-Teodor <berindeie.teo at gmail.com> wrote: > On Wed, Oct 3, 2018 at 2:44 PM Timo Sirainen <tss at iki.fi> wrote: > > On 3 Oct 2018, at 14.09, Berindeie Avram-Teodor <berindeie.teo at gmail.com> > > wrote: > >> On Wed, Oct 3, 2018 at 1:53 PM Timo Sirainen <tss at iki.fi> wrote: >

Folks, Am 20.06.2016 um 22:01 schrieb Larry Irwin (gmail): > The scripts I use analyze the rsync log after it completes and then sftp's a summary to the root of the just completed rsync. > If no summary is found or the summary is that it failed, the folder rotation for that set is skipped and that folder is re-used on the subsequent rsync. > The key here is that the folder

On 3 Oct 2018, at 14.09, Berindeie Avram-Teodor <berindeie.teo at gmail.com> wrote: > > > > I do not have downloaded the source from GitHub. The patch modifies configure.ac, so unless you run autogen.sh the configure script isn't modified and that patch doesn't work. Or as an alternative you could simply manually append to config.h: #define HAVE_CRYPT_H > >

> On 04 October 2018 at 11:05 Florian Pritz <bluewind at xinu.at> wrote: > > > On Wed, Oct 03, 2018 at 03:47:11PM +0300, Berindeie Avram-Teodor <berindeie.teo at gmail.com> wrote: > > On Wed, Oct 3, 2018 at 2:44 PM Timo Sirainen <tss at iki.fi> wrote: > > > On 3 Oct 2018, at 14.09, Berindeie Avram-Teodor <berindeie.teo at gmail.com> > >

https://bugzilla.samba.org/show_bug.cgi?id=11521 Bug ID: 11521 Summary: rsync does not use high-resolution timestamps to determine file differences Product: rsync Version: 3.1.2 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 Component: core

I downloaded the latest version of puppet 2.6.0 today, and still can''t get parameterised classes to work. At least, I think it''s 2.6.0... the version number in the RPM spec file says 0.25.5. This simple example: /etc/puppet/manifests/nodes/pax/name01.pax.xxx.com.pp: node ''name01.pax.xxx.com'' { class { amodule::afunc: version => "1.0" } }

Thank you. Now it is working! On Wed, Oct 3, 2018 at 2:44 PM Timo Sirainen <tss at iki.fi> wrote: > On 3 Oct 2018, at 14.09, Berindeie Avram-Teodor <berindeie.teo at gmail.com> > wrote: > > > > >> I do not have downloaded the source from GitHub. >> > > The patch modifies configure.ac, so unless you run autogen.sh the > configure script