Freefilesync temp files on writelocked device
- Posts: 5
- Joined: 1 Apr 2010
The newest version of freefilesync, version 5.16, handles writelocked devices different than the earlier versions. Now it wants to store the temp file of FFS on the device it will synchronize. If these are writelocked, there is a errormessage and it won't synchronize the specific device. Earlier versions of FFS worked OK with writelocked devices. Is this a bug? And if so, will it be fixed in a newer version of FFS?
-
- Site Admin
- Posts: 7170
- Joined: 9 Dec 2007
The locking behavior is the same as in previous releases, but an error when writing the sync.ffs_lock file is no longer suppressed. You have multiple choices:
1. If it is possible that multiple FFS instances can access a folder at the same time, make sure that FFS has write access to save the lock file.
2. If you are the only user and only ever run a single instance of FFS at a time, you may ignore the error and select "don't warn again". FFS will still try to lock a directory, but won't show a warning message anymore if it fails to do so. This is equivalent to handling before v5.16
3. Disable the lock file alltogether (see help file, chapter "Expert settings"). FFS will not even attempt to write the lock file. You should only do this if you can guarantee that there is no conflict of multiple FFS instances accessing a directory, and if there is an actual benefit, e.g.
[404, Invalid URL: https://sourceforge.net/p/freefilesync/feature-requests/186/]
1. If it is possible that multiple FFS instances can access a folder at the same time, make sure that FFS has write access to save the lock file.
2. If you are the only user and only ever run a single instance of FFS at a time, you may ignore the error and select "don't warn again". FFS will still try to lock a directory, but won't show a warning message anymore if it fails to do so. This is equivalent to handling before v5.16
3. Disable the lock file alltogether (see help file, chapter "Expert settings"). FFS will not even attempt to write the lock file. You should only do this if you can guarantee that there is no conflict of multiple FFS instances accessing a directory, and if there is an actual benefit, e.g.
[404, Invalid URL: https://sourceforge.net/p/freefilesync/feature-requests/186/]
