similar to: exclude hidden files

I have been using rsync on and off for years, but it still has the ability to throw me on more occasions than I care to admit:-) Currently I am trying to obtain a better understanding of the --include and --exclude options. Even though I think I have a pretty good understanding of the basic mechanics of these options and can usually get things to work as I want, there are a couple of issues that

On 06/03/2023 08:56, belaz--- via samba wrote: > Yes, I've deleted the main samba package and the service is not running now. But was it running when you tried the command ? > Tried what? The command. > Logs must be created automatically, without my effort. They are, but only if smbd etc are running. > All this questioning sucks - it just wastes my time. Can I point out that

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

Hi all, I am having *massive* problems trying to exclude a single directory from an rsync. I have serv1 and serv2. I am trying to rsync /foo/test from serv1 to /foo on serv2 I want to exclude the directory /foo/test/dir1 So I try: rsync -av --exclude-from=/foo/rsync.excludes /foo/test serv2:/foo rsync.excludes contains: /foo/test/dir1/ This is not working. I also try: rsync -av

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, I used --partial to transfer files from my local computer (rsync 3.1.2, Debian) to a remote computer (rsync 3.1.1 WD MyPassport Storage device) The files get transferred, but after successful transfer, the files are not renamed from .<tmpfile> to <file>. Where to go next? Here is the verbose output after transferring an empty file heiko at blade:~/Pictures$ rsync

I've been using 3.0.0pre8 to move a Debian archive from one filesystem to another. This archive contains a daily snapshot of the Debian ftp site, with common files hardlinked to save space. I noticed that it was using far more space than necessary. Upon investigation it seems that all the source files that have inode numbers greater than 2^31 aren't being hardlinked together at the

Hi, Linux-Ubuntu here. English is not my first language. The man rsync is difficult to understand. I want to backup some folders recursively and some files, see [1] in my /home dir to an external USB HD (Ext4). I want to use a text file for the purpose. [1] /home/user/Documents /home/user/Software /home/user/.evolution/addressbook/local/system/addressbook.db

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

I work on software that archives gigabytes of files to multiple sites. Occasionally one or two files have no read permissions: % ls -l dir/foo --w-------+ 1 abcserve myusers 11222 Jan 10 03:14 The error message is: rsync: send_files failed to open "/dir/foo" (in xxx): Permission denied (13) rsync error: some files/attrs were not transferred (see previous errors) (code 23) at

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

Hi All, I'm trying to run nls on the data from the study by Marske (Biochemical Oxygen Demand Interpretation Using Sum of Squares Surface. M.S. thesis, University of Wisconsin, Madison, 1967) and was reported in Bates and Watts (1988). Data is as follows, (stored as mydata) time bod 1 1 0.47 2 2 0.74 3 3 1.17 4 4 1.42 5 5 1.60 6 7 1.84 7 9 2.19 8 11 2.17 I then

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

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 have a problem with using rsync between a RH Linux 9 rsync server and an ARM based device running what is basically debian linux. RSYNC versions are 2.5.5.4 and 2.6.0 (or 2.5.5, makes no difference) respectively and I have been testing with a set of about 50 files. The ARM machine has no display, but when logged in via telnet I can run a shell script that performs the synchronization and

Hi All, I'm trying a remote backup for the first time. It is between two laptops, I installed rsync 3.0.7 on both compiled patch -p1 <patches/fileflags.diff patch -p1 <patches/crtimes.diff patch -p1 <patches/crtimes-64bit.diff patch -p1 <patches/crtimes-hfs+.dif f patch -p1 <patches/hfs_compression.diff ./configure make this all works perfectly for local backups, clones

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

Hi, I''m looking for qualified Ruby on Rails developers to work on a client web portal project in Midtown Manhattan for a large financial research company. Requirement Overview: Ruby / Ruby on Rails developer with strong object oriented programming background. Good understanding of model driven architecture, MVC, RDBS and data modeling. Required Skill Set: - BS. in Computer Science (or

I'm generating a list of files to sync, and would like all the files not in my list to be deleted from the destination. I thought that --delete-missing-args would do just that, but it doesn't delete anything. Would someone have an idea of what I'm doing wrong? This is what I tried : ~$ mkdir -p /tmp/source /tmp/dest ~$ for i in {1..3}; do echo "keep $i"      >

I go thru this every few mnths it seems. Rsyncs exclude rules are very sophisticated but because of that somewhat unfathomable at times. Simplified: I want to exclude directories named no_bak anywhere in the tree but only the files under them, not the direcrories themselves. My exclude rules look like: no_bak/* /no_bak/* The first one does catch directories by that name on the first level but