search for: kittenberg

...2, which does not look so cool. The other alternative would be to directly link with the rsync files (the possibilities of the GNU world), and call /use its according functions just like the rysnc main() function would do. What do you think would be smartest strategy to go for? Kind regards, Axel Kittenberger -------------- next part -------------- HTML attachment scrubbed and removed

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

Okay, I gave up fixing that raspberry and going to use some conventional legacy PC instead and reinstall it all. Is there a way I can use the group, user and domain controller IDs from the backups I created to reinstall a new Samba4 DC without the clients noticing? I don't like to rejoin everything yet another time. - Axel

On Thu, 9 Feb 2017 10:55:51 +0100 Axel Kittenberger <axkibe at gmail.com> wrote: > > Has someone experience with collecting the changed files > > with a third party tool which detects which files were changed? > > I don't know of sysdig but am the developer of Lsyncd which does > exactly that, collect file change...

https://bugzilla.samba.org/show_bug.cgi?id=12569 Bug ID: 12569 Summary: Missing directory errors not ignored Product: rsync Version: 3.1.2 Hardware: All OS: Linux Status: NEW Severity: normal Priority: P5 Component: core Assignee: wayned at samba.org Reporter: axkibe

Am 09.02.2017 um 16:21 schrieb Ben RUBSON: > >> On 09 Feb 2017, at 16:10, Thomas Güttler <guettliml at thomas-guettler.de> wrote: >> >> Am 09.02.2017 um 11:05 schrieb Ben RUBSON: >>>> On 09 Feb 2017, at 10:05, Thomas Güttler <guettliml at thomas-guettler.de> wrote: >>>> >>>> Hi, >>>> >>>> we have a huge

https://bugzilla.samba.org/show_bug.cgi?id=12781 Bug ID: 12781 Summary: rsync library Product: rsync Version: 3.1.3 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 Component: core Assignee: wayned at samba.org Reporter: ildar at altlinux.ru

I never figured out how I should tread error 13 from rsync, "Problem with diagnostics". My question is, is this a transient or permanent error? Or how seriously did something go wrong when rsync returns 13? I don't get much smarter reading the rsync source either. For reference this is for Lsyncd, which watches files with inotify and uses rsync to transmit changes to a slave. It

On Thu, 9 Feb 2017 14:43:57 +0100 Axel Kittenberger <axkibe at gmail.com> wrote: > > > > Not only that, but inotify is not guaranteed. (At least not on > > 3.16.0. Can't say regards later versions.) So you might miss some > > changes. > > > > Got any info on that? > > I noted that MOVE_FR...

Hi, we have a huge directory tree. * 17M files (number of files) * 2.2TBytes of data. * Only 0.1% changes per day Current pain: rsyncs directory tree traversal needs to long to discover the changed files. Only few files change. I discovered the tool sysdig which could be used to monitor the files which were changed. Then we could feed the list of changed files to rsync and avoid the

Exit code 2 is "Protocol incompatibility". Also, sounds like what you really want is --files-from On 04/07/2017 10:01 AM, Axel Kittenberger via rsync wrote: > With this two options on a very live system you may need to take into > account this bug as well I reported a while ago: > > https://bugzilla.samba.org/show_bug.cgi?id=12569 > > Due to this I'm currently not using --ignore-missing-args / > --delete-m...

Dear All, We sometimes have to replicate large "live" filesystems with many ( sometimes millions, up to few hundred millions ) files on them. ( Copying actively used files is of course a bad idea, but it really helps to keep the delta small, so one final transfer can later save the day. ) The problem, as one may guess, is that some files may disappear during the process, so rsync

Hello, I'm using a Rasperry:Pi as Samba4 DC for a small computer lab (9 clients). Unfortunally I just had a crash with a broken ext4 filesystem. However, I got a full image of the SD card just after I finished installation and connected all domain clients a few days ago. I can simply dd that over a new SD card and be running again. However, that image has not all the users I created since

Dear rsync-list, I got following issue demonstrated by this script: ----- $ mkdir -p src/a trg/a $ echo "/a/b/c" > list $ /usr/bin/rsync -slt --ignore-errors --force --ignore-missing-args --delete-missing-args --files-from=list src localhost:`pwd`/trg file has vanished: "/home/axel/src/a/b" ABORTING due to invalid path from sender: a/b/c rsync error: protocol

> Has someone experience with collecting the changed files > with a third party tool which detects which files were changed? I don't know of sysdig but am the developer of Lsyncd which does exactly that, collect file changes via inotify event mechanism and then calls rsync with a matching filter mask. However, since you say, your directory tree is hugh, the main issue is that for every

With this two options on a very live system you may need to take into account this bug as well I reported a while ago: https://bugzilla.samba.org/show_bug.cgi?id=12569 Due to this I'm currently not using --ignore-missing-args / --delete-missing but rather -exclude=* -include=- and a autocreated hierachical filter rule list on stdin. PS: Yes to simply ignore code 24 would be correct.