You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was just looking through the code and was wondering about the following case:
slave A removes a file while slave B updates the file.
In this case I would guess that a convenient way to procede would be to update the file and not delete it.
From what I saw, the script does it the other way around. Is this the desired outcome?
Thanks
Tom
The text was updated successfully, but these errors were encountered:
Yeah, this is one of these cases where it is hard to define correct behavior. In this case also it's hard to say who "is right", A or B. For safety it would be better to keep updated file because it may include new important content. Unfortunately rsync doesn't keep any log with deletion/update times so it can't tell if the file that was deleted on A (and thus removed from "master" store) should be restored from A's copy. Adding workaround for this case would require a lot of code (and almost implementing light scm) and I'm not planning to do this. If you feel it's crucial you can fork and try implementing such an improvement. If it appears to be light solution than I will happily merge it.
hi,
I was just looking through the code and was wondering about the following case:
slave A removes a file while slave B updates the file.
In this case I would guess that a convenient way to procede would be to update the file and not delete it.
From what I saw, the script does it the other way around. Is this the desired outcome?
Thanks
Tom
The text was updated successfully, but these errors were encountered: