similar to: pattern geeks?

Hello All, When i run lsyncd using *lsyncd -rsync /home/abc/source /home/abc/dest*then i am able to sync the two directories of the local system. But when i run using *lsyncd -rsync /home/abc/source 10.5.1.12:/home/abc/dest* where 10.5.1.12 is the ip address of the local machine then i am unable to sync the both directories on the local machine. Please leave your suggestions. Thank you, --

Hi, I'm running rsyncd in daemon mode started via xinetd. My /etc/rsyncd.conf looks like: [cache] path = /mnt/tst_vol_aws/sat_p_cache/ comment = Cache Directory use chroot = false read only = false uid = someone gid = someone dont compress = * On the client I run: /usr/bin/rsync --delete --ignore-errors -gpzsoltD --temp-dir=/mnt/tst_vol_aws/tmp/rsync -r

Let's say I have a slow, or high latency (or both) link between two hosts, and transferring data is expensive. Is it possible with rsync (or any other tool like rsync) to maintain a local metadata cache, such that I can rsync without transferring data to and from the hosts about what files are already in place ? That is, I already "know" what is out there and don't need to

Hi Friends, I am using rsync to copy data from Production File Server to Disaster Recovery file server. I have 100Mbps link setup between these two servers. Folder structure is very deep. It is having path like /reports/folder1/date/folder2/file.tx, where we have 1600 directories like 'folder1', daily folders since last year in date folder and 2 folders for each date folder like folder2

Hello All, Myself Garvit Sharma working in hyderabad central university(HCU) at DCIS. I have started using rsync to sync the data and i found it very interesting. After using rsync a lot i realized to contribute to rsync by adding some extra features into it. Every time for synchronization we need to do it manually by executing command on the command line but instead of doing it

You could try using an automounter, like autofs, in combination with sshfs. It'll be slower, possibly a lot slower, but it should be more reliable over an unreliable connection. I've been using: remote -fstype=fuse,allow_other,nodev,noatime,reconnect,ServerAliveInterval=15,ServerAliveCountMax=40,uid=0,gid=0,ro,nodev,noatime :sshfs\#root at remote.host.com\:/ BTW, I'm not sure

For backuping system folders on ArchLinux I use the following command per folder: rsync --update -DHAErlptgo --relative --delete-during $dir $backupdir The problem is that every file in /root folder and its subfolders is copied each time when this command is run. In all other folders only new or modified files are copied. The files and the folder itself have the following attributes: [root at

Before anyone yells at me, yes, you can use rsync's --checksum to detect (and fix) files that are incorrect despite having correct timestamps and sizes. This would mean that a previous rsync had been corrupted not the current one. But it is important to note that this would only be reported to you if you also use --itemize-changes and what to look for (a file with a c but not an s or a t).

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]

Ok, thank you for this extra info. I have experienced exactly what you described. The rsync dry run is _still_ running after being started at 1:30am PST :) But it is finding the right files to update. Most of the entries are: >fc........ Which is what I want. So, just because I see: >f at the beginning... That doesn't necessarily mean that the file is going to get updated at the

Hello, I'm author of Lsyncd - the live syncing deamon - http://code.google.com/p/lsyncd/ - a daemon that uses Linux` inotify to watch for filesystem changes - aggregates them for a few seconds and then periodically calls rsync to transfer the changes to target(s). Version 1 was simply aware of directories only, and it called rsync once with --delete -d for every directory in which anything

On Fri, 27 Apr 2018 22:40:41 +0100 Jonathan Hunter via samba <samba at lists.samba.org> wrote: > OK - some more detail I have found in the meantime. > > I have compiled & ran listxattr, and I can now see a difference > between a working and a broken file: > > me at dc2:~/download $ > sudo ./listxattr /usr/local/samba/var/locks/sysvol/ >

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

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 You didn't say if you were networking or what features of rsync you are using but if you aren't networking and aren't doing anything fancy you are probably better off with cp -au which is essentially the same as rsync -au except faster. Anyways, smaller reads and writes are usually better handled by the OS's caches than really big

Hi, I've configured 'backuppc' to transfer files via rsyncd, with enabled checksums. Whith one of the shares I get the error (in syslog): --------------------------------------------------------------------- robbe rsyncd[2183]: ERROR: out of memory in receive_sums [sender] robbe rsyncd[2183]: rsync error: error allocating core memory buffers (code 22) at util2.c(106)

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

On 2015-04-14 11:25, Gordon Messmer wrote: > On 04/14/2015 11:07 AM, Florin Andrei wrote: >> I looked in the yum repositories for CentOS 7 and I noticed that there >> are no packages for any of the major open source IPSec VPN apps - >> Openswan, strongSwan, etc. I'm pretty sure CentOS 6 had Openswan >> packages. > > libreswan replaced openswan, and is

What about -c? It seems I'm getting a lot of spurious file transfer candidates when using: -avvznIi --no-o --no-g --no-p It's showing transfers (receive) for many files I know haven't been tampered with. Thanks, -Clint On Tue, Oct 27, 2015 at 7:53 PM, Kevin Korb <kmk at sanitarium.net> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > That is correct.

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

I apologize in advance for asking a beginner question, but I really could not figure this from the manual page. I want to copy some files with rsync, and not copy others. The stuff that I do not want to copy looks like this: System Volume Information/_restore*/RP* WINDOWS/Prefetch/* Documents and Settings/leila/Local Settings/Application Data/Google/Chrome/Application/*/Installer/chrome.7z