Release notes for build #1871, release June 6, 2019

Build 1.16.1871 


*Windows NTFS permissions support*

- Windows NTFS permissions support now available for all existing and new filespaces

- Allow seamless usage of LucidLink on Windows machines managed by a central domain controller

- Support for all permissions (Open file or folder properties->Security tab)

- Implementation is perfectly suited for service setups, where Lucid filespace is exposed through a share and individual users do not know the filespace username and password. (see limitations below)

*Windows NTFS permissions current limitations*

- Auditing (see Auditing tab under Advanced settings) is currently not supported

- Windows Lucid clients with version older than 1.16.1871 will ignore all NTFS permissions set. Can mitigate this concern by:

    - either assuring that all Windows Lucid clients connecting to the filespace are version 1.16.1871 or newer

    - ...or initialize a new filespace using 1.16.1871 Lucid client to ensure no older Windows Lucid clients can connect

- Any Linux or macOS Lucid client that connects to a filespace will ignore all NTFS permissions set

*Client enhancements:*

- `lucid status` now shows connectivity state to the LucidLink service as well as the connectivity state to the object store

- Improved bandwidth utilization during upload of big files (1GiB+)

- Added more verifications on --reky-s3 command to check for all the necessary S3 endpoint permissions

- Optimized layout of the metadata DB resulting in less storage, RAM and CPU usage

Bug fixes:

- [macOS] Fixed an issue where macOS will increase CPU usage significantly upon receiving high volume of file changes from other clients connected to the filespace. (edited) 

Login or Signup to post a comment