similar to: Yet another filter question

I hate to say anything remotely negative to Wayne but... That wording from the man page makes almost no sense without the examples directly after it (and I have read it many times and know what it is saying). When I go all RTFM on this topic I usually tell them to 'man rsync', search for file-will-not-be-found and start reading from that line. Once you understand the broken and correct

I thought this command would do what I wanted, but instead it doesn't transfer any files: rsync -avh --stats --password-file=/var/rsync.passwd --include=Maildir/ --exclude=* mail::root/usr/home /backup/usr/ I want to backup ONLY the /usr/home/*/Maildir directories. I don't want any other files from any other directories to be transferred. I can see in the man page where this is a

On Wed, 4 May 2016 21:09:44 -0400 Kevin Korb <kmk at sanitarium.net> wrote: > That wording from the man page makes almost no sense without the > examples directly after it (and I have read it many times and know > what it is saying). Makes sense to me. The only thing I'd change is to use "in a depth first fasion" instead of "from the top down", "depth

Given the structure… /foo/bar/want-this.txt /foo/bar/want-this-2.txt /bar/foo/ /do-not-want-to-transfer/test.txt With the desire to ‘include items with foo in their path’... I understand that the closest I can get to a satisfactory filter ruleset is something like: + **foo** + */ - * … and setting --prune-empty-dirs. However, /bar/foo/ is empty, and of course should be copied.. but is pruned.

I was under the impression that --include and --exclude worked by matching patterns in the order given, and whichever matched first, whether that was an include or exclude determined the action for that file. I have a big directory from which I am attempting to transfer selected files. I want all files where the first level directory is anything, the second level directory is "2005"

Hi All, I wanted to send a follow-up mail to the C API discussion/BoF that we had at the latest developer meeting and nicely hosted by Justin and Juergen. We were able to reach consensus on a number of questions/concerns about the C API so I’m going to go ahead and list them for posterity and for any further discussion here: Stability Guarantees: The C API is, in general, a “best effort” for

"Documentation: We’re going to document this policy in the developer documentation. In addition, any changes to the C API will require documentation in the release notes so that it’s clear to external users who do not follow the project how the C API is changing and evolving." So, yes? -eric On Thu, Nov 19, 2015 at 5:55 PM Sean Silva <chisophugis at gmail.com> wrote: > Are

On Tue, Mar 20, 2018 at 5:49 PM Kevin Korb <kmk at sanitarium.net> wrote: > Nothing there should be preventing incremental indexing. That means it > should start copying as soon as it finds a file that needs to be copied. > Doesn't it tries to create all (empty) directories first? > On 03/20/2018 02:33 PM, Bráulio Bhavamitra wrote: > > > > > > Em seg, 19

On 7/24/2017 8:39 PM, Nico Kadel-Garcia wrote: > > Why are the targets of the hardlinks evaporating on rebooting? Is that > a FreeBSD'ism? Its when syslogd stops/starts. The hardlinks need to be recreated for some reason. ---Mike -- ------------------- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, mike at sentex.net Providing Internet services since 1994

OK. Thanks. Where can I find information regarding how to interpret —itemize-changes? The timestamps aren’t changing, so the target must not be storing them, which I have no idea why. The directory I’m writing to is 777. What is the flag to tell rsync to ignore the timestamps? Thanks, Blake On 6/2/16, 6:18 PM, "rsync on behalf of Kevin Korb" <rsync-bounces at lists.samba.org on

Em seg, 19 de mar de 2018 11:34, Kevin Korb via rsync <rsync at lists.samba.org> escreveu: > The performance of rsync with a huge number of files is greatly > determined by every option you are using. So, what is your whole > command line? > rsync -avP /data-old/ /data > > On 03/19/2018 09:05 AM, Bráulio Bhavamitra via rsync wrote: > > Hi all, > > > >

Thank you! I run --times when I use rsync (I actually use the -a flag) but the times do not transfer over and if I run rsync dryrun with -i I can see that it wants to transfer the files because of times. When I run rsync a second time with your suggestion the times do transfer over. I don't know why... B ________________________________________ From: rsync [rsync-bounces at lists.samba.org]

Thanks Kevin! I¹m unclear how to read the ‹itemize-changes output. Can you provide some insight? This is a local transfer from an external drive to an internal drive all attached to one computer. rsync -aPh --itemize-changes -n /Volumes/shuttle_05/2012_79_1_14_1__1199_Workprint /Volumes/3TB_LTO/LT003A/ sending incremental file list >f..t.......

How do I transfer just the modification times with rsync? I now the file content is the same but the modification times are different. Is there a way to do this? Every way that I have tried causes the whole file to transfer as well. Thanks -------------- next part -------------- An HTML attachment was scrubbed... URL:

Cool Thanks! Specifically, the timestamps on both <src> and <dest> match for "ls -l" but do not match for "ls -lu" or "ls -lc” The storage is just an regular HDD in a mac pro tower. I can’t imagine why it wouldn’t handle timestamps. Also of note - this problem doesn’t exist for every file, just the vast majority. So, that just makes it more confusing. Yes,

Hi Kevin, I haven't specified --whole-file. After entering an rsync command the terminal always reads "delta-transmission disabled for local transfer or --whole-file" but I assume that is just a standard phrase that always appears. So, if I am running partial (-P) and not using --whole-file or disabling the delta-transmission, why would an incomplete file be deleted and the

I would like to push a file, /home/cfg/temp, from client to a server with rsync in daemon mode to /n2p/cfg directory. How should I set the filter/include/exclude parameters on the server side rsyncd.conf file so server will disallow receiving any files from the client other than /home/cfg/temp? -------------- next part -------------- An HTML attachment was scrubbed... URL:

On Sat, 18 Apr 2015 00:39:42 -0400, Kevin Korb wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > I still don't see an output from rsync --itemize-changes with an A/B > difference. What do you mean by saying the above things? Do you mean only the `--itemize-changes' is enough for my case? Or Do you want to see the output from my case of running on the

I use --filter='dir-merge .backup-filter" to allow my users to designate portions of their home directories that should be excluded from my rsync-based backup system. I'm looking for a way to periodically generate a report that shows the amount of backup space being used by each user. I've tinkered with writing my own script that processes any filter files into --exclude

rsync in daemon mode is very powerful, yet it comes with one big disadvantage: data is sent in plain. The workarounds are not really satisfying: - use VPN - one needs to set up an extra service, not always possible - use stunnel - as above - use SSH - is not as powerful as in daemon mode (i.e. read only access, chroot, easy way of adding/modifying users and modules etc.) Why was encrypted