Quote:
Originally Posted by BetterRed
@ilovejedd - does FFS write anything to the source and target device, I'm thinking of its version history, logs etc.
Goodsynch writes its stuff to hidden directories at the root of the source and destination devices - i.e out of harms way, and where they can do least harm.
However I recall seeing another file sync tool that sprinkled stuff in the directories selected for syncing. So if you mirrored D:\Calibre\Calibre Library to E:\Calibre\Calibre Library, it would write 'control' data into those directories which would generate errors in Check Library. I can't recall if FFS was the culprit or the solution.
|
The
sync.ffs_db is optional. It's only created if you select certain settings. I think it was if you enable keep track of moved files? In any case, it's just a single file and it'll be in the same location as metadata.db so quite easy to add to exceptions for Check Library.
Logs are stored in the user's AppData folder by default, iirc.
As mentioned, FFS does create a temporary lock file during sync which gets deleted right after.