Usage: lucid3 daemon [options] Start the daemon/service in interactive mode Options: --instance id Specify the daemon instance, when running multiple instances --fs name The filespace name --rest-endpoint endpoint Specify the REST service TCP ip:port --ephemeral Don't read/save the configuration into the config file --config-path arg Specify the path where the .json config file is located --user username User used to link to the Filespace. --password password User's password [--mount-point] path Mount the Filespace at this mountpoint --label name Windows only. The label of the Filespace drive. --root-point path Folder within the Filespace to appear as the root folder. Path starts at the lucid3 Filespace root. [--no-mount] Don't mount the Filespace after linking --no-progress Don't print link/unlink progress --allow-reset-local-fs Allows resetting of the local file index and data cache if inconsistency detected (e.g. caused by forceful shutdown) --reset-cache-location Reset to default data cache location --root-path path Set root path for the Filespace data and metadata [--all-snapshots] Activate in snapshots mode --snapshot id Activate the snapshot instead of the live Filespace --proxy arg Specify a proxy server to tunnel all communication. Use the following format: [protocol://][user:password@]proxyhost[:port]. Supported protocols: http. Not applicable for Azure object storage.
Windows:
lucid3 daemon --fs <filespace.domain> --user <fsuser> --password <fsusrpwd> --mount-point L:
Linux/macOS:
lucid3 daemon --fs <filespace.domain> --user <fsuser> --password <fsusrpwd> --mount-point /media/filespace
Note: --mount-point can be folder path or drive letter (Windows only)
(Linux/macOS)--fuse-allow-other
enables other users to access the Filespace mount-point.
For OSX, ensure you are a member of the macfuse Admin group.
For Linux, editfuse.conf
and uncomment (remove#
).
nano /etc/fuse.conf
user_allow_other
Alternatively, runsed -i 's/#user_allow_other/user_allow_other/g' /etc/fuse.conf
For security purposes it will make sense to hide the password from daemon process lists.
It is recommended you secure a password file containing your Filespace user password to parse to the daemon, this ensures only your user has authority to read its contents.
Windows:
powershell -command "type pwd_file | lucid3 daemon --fs <filespace.daemon> --user <fsuser> --mount-point <mount>"
Linux/macOS:
cat pwd_file | lucid3 daemon --fs <filespace.daemon> --user <fsuser> --mount-point <mount>
Validate the process:
ps xuaf | grep lucid3 | grep daemon
Also see Link to multiple Filespaces on the same client and Link to a Filespace with a specific cache and metadata location.