Hi,
Just one comment on issue (6).
a. I did AB sync. Files added to A and B from each other.
b. Then I did BC sync. Files added to b and C from each other.
c. I went back to A (which had been off throughout so no new files added). I did AB sync expecting new files from B (as received from C) to be sent to A, thus having same files on ABC.
Strangely, FFS didn't send ANY new files from B to A.
Instead it wanted to ONLY send files from A to B again, including files that were already on B.
Totally confused where the logic in this is?
Just realised this was my silly error.
When I went back to AB, for some reason the setting file wasn't actually pointing at B properly hence the confusion.
I corrected the B path and now FFS is acting perfectly by sending all new files from B (as taken from C), into A.
This is exactly what I wanted, so now ABC will all be the same.
Moving onto the issue you stated about ff_db file only being for 1 machine, I will have to see if this creates problems in the future. For now it seems to work fine.
I'm hoping I'll be able to sync machines A,C using offline hdd B and/or online cloud D.
If there are problems, might consider Unison as its manual says it can sync ABCD fine because its logic is to work in pairs only. AB, BC, CD, DA. If FFS could do this, perhaps it would overcome the current limitations on multi machine sync.
Will test further and update.
Thanks
]]>