Important points about CLC Server File System Locations
- The directory on the file system configured as a CLC Server File System Location should be dedicated for use by, and should only be directly accessed by, the CLC Server. Files should not be moved manually into this directory or areas under it, for example using standard operating system's command tools, drag and drop, and so on.
- The underlying file system must support file locking.
- Directories configured as CLC Server File System Locations must have file system permissions enabled for the user that runs the CLC Server process as it is this user that will own files written to these areas by the CLC Server.
- A directory configured as a CLC Server File System Location should not be a subfolder of, or otherwise overlap with, another directory configured as a CLC Server File System Location. Overlapping File System Locations lead to problems with indexing.
- Rebuilding indexes for File System Locations with a very large number of data elements can take a long time. Having multiple smaller locations, rather than a single very large one, can help minimize the time needed if re-indexing has to be carried out.
Further information about indexes can be found in CLC Server File System Location indexes.