I do this sort of thing between my home and work machines, but only one
system changes at a time, and I do a sync in the appropriate direction at
the end of each session.
I think what you want may not be possible, since rsync doesn't maintain
any database about the files it handles and deleted files have no date
stamps associated with them. I think you need full blown distributed file
system.
Britton Kerin
__
GNU GPL: "The Source will be with you... always."
On Mon, 25 Jun 2001, Kovalev, Ivan wrote:
> I am doing a "poor man cluster" using rsync to synchronize content of 2
> servers each of which has its own directly attached storage. Since it is a
> cluster (load balancer on top of these 2 servers), new additions as well as
> deletions might appear on any of the 2 servers.
>
> Newly added files are replicated just fine, but I need list's wisdom on how
> to replicate deletions.
>
> Suppose I have a new file on server1 and it is pooling from server2 with
> --delete option. Then my new file will be deleted because it is not present
> on server2. If I do push from server1 to server2 without --delete as a first
> step (to make sure new file is there by the time I will pool), then I will
> also push old files from server1 which were deleted on server2 since last
> synchronization. This will effectively kill replication of deletions.
>
> The problem would be solved if rsync had a way to do updates compare to the
> known system state. I mean if I could direct it to replicate only the
> changes that were done after time T.
>
> I did not find anything like this in man pages or list's archives for last
> few months, but the question seem to be so obvious, that I am probably
> missing something.
>
> Ivan Kovalev
> Thomson Financial, BFMG / IBES
> 195 Broadway, 6-th floor
> New York, NY 10007-3100
> [EMAIL PROTECTED]
> tel. (646)822-2939
> fax.(646)822-2800
>
>
>
