File locking functionality allows multiple people to collaborate on the same files/folders without accidentally overwriting each other's edits. However, the locking semantics are largely dependent on the native capabilities provided by the applications based on the opens and/or the location from which the files would be accessed. Resilio recommends the following best practices for file locking in certain use cases and applications. Admins might have to exclude the following file types from file locking to allow seamless simultaneous access.
EPLAN
The EPLAN application creates the LCK file, maintains its own locking semantics, and doesn’t honor the shared file locks created by the Resilio lock server. As a result, file access issues arise, and eventually, the files become read-only. To avoid data unavailability, Resilio recommends excluding EPLAN files and file extensions and any others based on your use case.
To exclude files, please add each one of the application extensions in a separate line: .eod, .eox, .flk, .lck, .elk, .slk, .xlk..eod, .eox, .flk, .lck, .elk, .slk, .xlk.
Rhinoceros 3D
The application uses .3dm.rhl files to maintain file locking information about the users' information (who, when, and where the file(s) were locked), preventing further file modifications. This is different from the regular file locking behavior
This read-only lock prohibits further file modifications, and subsequently, the existing Rhinoceros file opens will not be visible in the list of Resilio File locks. To view and manage the Rhinoceros file locks from the Resilio Management Console, please add the custom parameter shared_locks_strict_access_checks:false to Job Profile.
FSLogix
FSLogix profile locking isn’t compatible with Resilio file locking. Accessing the FSLogix profiles before they are synchronized stalls the sync process, which will not resume until the users stop accessing them.
This is due to the native FSLogix behavior, which only allows read-only access to previous versions of the profile while the new ones are being downloaded from other agents. This leads to a soft deadlock, wherein the Resilio agent is unable to update the profile to the latest downloaded version as it has read-only access to the previous version. To avoid this, Resilio recommends excluding FSLogix profiles from the file locking.