What determines the location of the sync.ffs_db files? Can they be located in a user specified location (and, if yes, how)?
I use the donation edition frequently & sometimes find the sync.ffs_db on both sides ...not sure why...I may be syncing a folder as primary to mirror to a backup folder and then later using that backup folder to mirror to another location...and then later noticing the sync files.
What determines the location of the sync.ffs_db files?
- Posts: 8
- Joined: 25 Dec 2024
-
- Posts: 2978
- Joined: 22 Aug 2012
viewtopic.php?t=10616#p40283
When using the database, after running your first sync, there is always a sync.ffs_db file in all your left and right base locations involved in your sync.
See also viewtopic.php?t=6045
When using the database, after running your first sync, there is always a sync.ffs_db file in all your left and right base locations involved in your sync.
See also viewtopic.php?t=6045
- Posts: 8
- Joined: 25 Dec 2024
Thank you, Plerry, your links were very helpful and answered my questions. The first link (& second) had a note from Zenju saying: "As a workaround it's always possible to set up some arbitrary pair of folders and "mount in" the real folders for synchronization with symlinks. This way you have control on where the database files are stored."
It has been a while since I used symlinks...but I tried setting up a couple of test folders but was unable to get it working the way I wanted. The symlink is working fine but when I select it in FFS it redirects to the 'real' directory and creates the sync.ffs_db file in the root. I tried all variations with the comparison settings (follow symlink, as link & not checked at all) with no change.
Is there any fuller explanation of Zenju's workaround? I would like to get the sync.ffs_db file in a different folder than my source files but still be able to detect moved and deleted files.
It has been a while since I used symlinks...but I tried setting up a couple of test folders but was unable to get it working the way I wanted. The symlink is working fine but when I select it in FFS it redirects to the 'real' directory and creates the sync.ffs_db file in the root. I tried all variations with the comparison settings (follow symlink, as link & not checked at all) with no change.
Is there any fuller explanation of Zenju's workaround? I would like to get the sync.ffs_db file in a different folder than my source files but still be able to detect moved and deleted files.
-
- Posts: 2978
- Joined: 22 Aug 2012
Never tried this myself, but (to me( the way to go seems to be:
Create an arbitrary folder A and define that folder as your the left base location for your FFS sync.
In said folder A create a symlink to your original left base location.
and/or
Create an arbitrary folder B and define that folder as your the right base location for your FFS sync.
In said folder B create a symlink to your original right base location.
In the FFS Comparison Settings (F7) checkmark "Include symbolic links" and select "Follow".
Obviously, the user under which credentials you run your FFS sync must (also) have read+write access to said folders A and B.
Create an arbitrary folder A and define that folder as your the left base location for your FFS sync.
In said folder A create a symlink to your original left base location.
and/or
Create an arbitrary folder B and define that folder as your the right base location for your FFS sync.
In said folder B create a symlink to your original right base location.
In the FFS Comparison Settings (F7) checkmark "Include symbolic links" and select "Follow".
Obviously, the user under which credentials you run your FFS sync must (also) have read+write access to said folders A and B.
- Posts: 8
- Joined: 25 Dec 2024
Really appreciate your help, Plerry. When I read your suggestion I thought "Of course! (and why didn't I think of that!)". After some tinkering your suggestion is working like a charm, thank you!
