On Thu, 2008-10-16 at 13:38 +0200, Axel Kittenberger wrote:
> For simplicity we just exec()ed the systems installed rsync binary to
> invoke rsync for a directory when a change happened in it. Now some
> users complained that this strategy involves a lot of forking on a
> vivid directory structure.
Thanks for your comment! But as you can see on lsyncd project base, we
compared it to rdbd (along other solutions) already. rdbd doesn't fit in
many cases, since in this usecase we want a oneway sync only, not a two-way
and rdbd is also a "heavy weight" solution, requireing big changes for
expost s
The solution needs to be around rsync? I think you should look in some
kind of "low level" replication, like drbd or something...
What you have described i think is something very complex, because you
can have many changes almost at the same time, and many sync process
starting, or so... i don´t kn
Dear list, I'd like to have your expertise opinion on following issue.
Out of a concrete need we developed an application that will rsync any
changes on a local directory structure to a remove system the moment they
happen using the linux kernel watch feature. This is in our opinion much
more eleg
