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 only 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.
- Data written to CLC Server File System Locations is owned by the user that runs the CLC Server process.
- Areas designated as file system locations should not overlap. That is, a directory configured as a CLC Server File System Location should not be a subfolder of another directory configured as a CLC Server File System Locations. Overlapping locations lead to problems with data indexing, which in turn leads to problems finding the stored data. Further information about indexing can be found in Rebuilding the index.