similar to: Does rsync need a --ignore-unreadable-files option?

I have been doing some experiments with rsync on btrfs, a copy-on-write file system that is approaching or having just achieved production-ready status depending on your requirements. For my purposes the reliability appears by almost all accounts to be there, and the compression alone makes it very compelling. However the following two experiments show rsync behaviors that are disappointing to

Hello, I'm trying to connect to one of the mirror sites to get a package update for Linux server through the proxy server, but after approximately 10- 15 minutes it times out with the following error: "rsync error: timeout in data send /received (code 30) at ioc (140) [receiver=3.0.9] rsync: connection unexpectedly closed (973 bytes received so far) rsync error: error in rsync

This is looking good and very helpful to an rsync novice. I will try the modification rsync --dry-run -avi --delete --filter 'protect /*’ --filter ‘protect /.*’ SOURCE/ TARGET/ and see what it produces. I do have a number of directories and files beginning with a dot in TARGET and these need to be protected. Unfortunately, the output from —dry-run is still likely to be sufficiently

Hi. On Tue, 16 Jul 2024 16:00:47 +0100 Chris Green via rsync wrote: > I run a daily backup using 'rsync -a -F ....' > I want to exclude everything in ~/.local/share **except** the file:- > /home/chris/.local/share/evolution/calendar/system/calendar.ics > I have the following in my rsync-filter file to exclude ~/.local/share > - .local/share > Can I simply add

Hi, On Mon, 13 Apr 2015 12:59:07 -0400 Kevin Korb wrote: > Hmmm, according to my interpretation of the man page (I am on 3.1.1) > that is supposed to work however when I test using the "-/ > /etc/passwd" example the / seems to have the same effect as commenting > the line. I get /etc/passwd copied whether the source is / or /etc. I guess that this -/ syntax is not usable

This avoids an error where the appliance cannot start up because this dbus helper script (which is never used) is unreadable by non-root. Why do we have unreadable binaries in Fedora at all? You may wonder: https://www.redhat.com/archives/fedora-devel-list/2009-October/msg00987.html Maintaining a blacklist like this is generally a bad thing. We should change this code so it automatically

I'm just starting with rsync(). I grabbed the 3.0.7 source and built it on Mac OS X.6.5 (./configure and ./make reported no problems.) When I try running with -X or -A, I get the following error messages: rsync: unpack_smb_acl: sys_acl_get_info(): Unknown error: 0 (0) rsync: unpack_smb_acl: sys_acl_get_info(): Unknown error: 0 (0) A quick look at the buglist didn't reveal anything to

Lately I've working on a backup script that utilize rsync together with MySQL logging. Everything has been working just fine until now when I needed to generate some errors for my error handling code. So I took a CD (which I scratched with a needle) and mounted it to the file system. There after I started the backup job which went on forever and never got completed. It seems that rsync

On Sat, 09 Jul 2011 15:04:24 +0200 Louis-David Mitterrand wrote: > Is there also a pure rsync solution (without any shell loop) maybe based > on --include/--exclude? I thing the following will do: cd /backup/current/home rsync -av --delete \ --include '/*/' \ --include '*/Maildir/***' \ --exclude '*' \ . /home Beware that the

On Tue, Jul 16, 2024 at 05:56:28PM GMT, Francis.Montagnac--- via rsync wrote: > > I want to exclude everything in ~/.local/share **except** the file:- > > /home/chris/.local/share/evolution/calendar/system/calendar.ics > > I have the following in my rsync-filter file to exclude ~/.local/share > > - .local/share > > Can I simply add the following before the

I second Francis here. You don't need to diagnose incomplete file transfers as long as you have racing conditions as you described. This leads to strange result inevitably. NEVER start several rsync jobs manipulating the same data - especially if there are modifications to BOTH sides source and destination. You do not necessarily define a service like Francis suggests. A simple semaphore

I hate to say it because it goes against my normal advice but this is one instance where using a * in the source parameter would help... rsync -vaiE --delete --dry-run source/* target/ This would ignore any top level directory that is on the target but not the source while rsyncing with --delete any top level directory that is on the source. It is normally recommended to not use a * in the

I want to exclude from the sync ALL files that start with a dot, IOW hidden files. But using --exclude '.*' does funny things with directories (or at least I think it does). Is there a recognised correct way to do this? I thought --exclude '.???*' would avoid the directory issue by only excluding any dot file(dir) with a name longer than 2 characters. Not tried it yet, but would

We have a number of scripts that use rsync to automate administration of a number our servers. We are adding servers that are not directly network accessible to our main admin box. That is, we have to go through an intermediate machine to reach these new machines. I've seen how you can string ssh commands together to copy commands through an intermediate machine. Does anyone know of a

On Mon, 13 Apr 2015 13:45:18 -0400 Kevin Korb wrote: > The +/- syntax absolutely works in an --exclude-from or --include-from > file I use it all the time. However, apparently the -/ syntax does > not work there. > So, I am not sure if the man page is wrong or if this feature just > isn't working correctly in an exclude file. This is perhaps this note in the "FILTER

Hi. On Sat, 04 Mar 2023 00:39:52 -0600 Albert Croft via rsync wrote: > The rsync commands may be launched from command-line or cron, but use > the same format and options in either case. As a result, there may be > multiple rsync processes pulling files from the same remote path to the > same local path. I think you should first prevent this to happen. If your receiving machine

hello, apparently,? rsync sorts the list of files? provided to "--files-from". how can i avoid sorting of that list ? I want to copy a list of files in specific order regards Roland

Hello, I think I found a bug in rsync. I checked the TODO and the issues, but I didn't find any reference to it. It seems, that rsync goofes up, if you rename a directory and then create a symlink with the old name to the new location. Below is a simple example how to do it. ------------------------------------------------------------------------------ [ptriller] elmore:~/test > ls

Hi. On Wed, 08 Mar 2023 22:21:28 +0100 Tomasz Chmielewski via rsync wrote: > After upgrading to rsync 3.2.7, the following command hangs forever > (using "--usermap" causes the hang; without "--usermap" it doesn't > hang): > rsync -v -p -e --usermap user:user /etc/services user at remote: This command is incorrect: the -e option needs a command. Without

Sorry if this problem has been covered previously. I'm having a problem with Rsync. I have created a script to put in cron but that is besides the point. Here is the script that i'm using. #!/bin/sh HOST=`/bin/hostname`