sudo nano /etc/systemd/system/lucidlink.service
[Unit]
Description=LucidLink Filespace Daemon
After=network-online.target
[Service]
Type=simple
#User=<user>
#Group=<group>
#WorkingDirectory=/home/<user>
ExecStart=/usr/bin/lucid daemon --fs <filespace.domain> --user <fsuser> --password <fsusrpwd> --mount-point <mount>
ExecStop=/usr/bin/lucid exit
Restart=on-abort
[Install]
WantedBy=multi-user.target
Passwords with special characters will require single ' ' or double " " quoting or sufficient escaping dependent on the special characters or consult our KB which leverages systemd-escape.
Modify accordingly the command-line arguments lucid daemon
--fs filespace.domain --user user1 --password password1 --mount-point
/media/filespace
You can create multiple systemd unit files for various lucid
daemon option --instance. Running separate instances for mounting multiple Filespaces, or mounting snapshots.
Each systemd unit file will require its own --instance <ID>. Include or exclude --root-path /media/cache.
Uncomment and modify systemd unit User, Group, WorkDirectory should you choose to run the service as a different Linux user, defaults to root and add lucid daemon option --fuse-allow-other see below.
Reload systemd daemon.
systemctl daemon-reload
Enable the LucidLink systemd service.
systemctl enable lucidlink.service
Start LucidLink daemon systemd service.
systemctl start lucidlink.service
Check LucidLink systemd service.
systemctl status lucidlink.service
If you have systemd error or the Filespace did not mount, or if you make changes to the systemd service you will need to reload the systemd daemon systemctl daemon-reload.
If no error in systemd service check Filespace mount-point exists.
ls /media/<mount>
Review the systemd service history.
journalctl -u lucidlink.service
Optionally if you would like to run your systemd service as a different user other than root, you can uncomment and specify the appropriate systemd unit User, Group and WorkingDirectory.
You can then provide the daemon --fuse-allow-other to enable other users on the same Linux machine to access the mount-point.
Note: Filesystem in Userspace (FUSE) allow_other is separate to user permissions. The user running the daemon controls their permissions, other users on the Linux system must have appropriate permissions.
Edit fuse.conf and uncomment (remove #) if you'd like the mount-point to be accessible to other users.
sudo nano /etc/fuse.conf
user_allow_other
Alternatively, run sed -i 's/#user_allow_other/user_allow_other/g' /etc/fuse.conf
[Unit]
Description=LucidLink Filespace Daemon
After=network-online.target
[Service]
Type=simple
User=<user>
Group=<group>
WorkingDirectory=/home/<user>
ExecStart=/usr/bin/lucid daemon --fs <filespace.domain> --user <fsuser> --password <fsusrpwd> --mount-point <mount> --fuse-allow-other
ExecStop=/usr/bin/lucid exit
Restart=on-abort
[Install]
WantedBy=multi-user.target
Reload systemd daemon
systemctl daemon-reload
Enable the LucidLink systemd service
systemctl enable lucidlink.service
Start LucidLink daemon systemd service
systemctl start lucidlink.service
Check LucidLink systemd service
systemctl status lucidlink.service
If you have systemd error or the Filespace did not mount, or if you make changes to the systemd service you will need to reload the systemd daemon systemctl daemon-reload.
If no error in systemd service check Filespace mount-point exists.
ls -la /media/<mount>
If seeing timeouts to due to slow network coming online in a virtual environment, try adding extra line after WorkingDirectory ExecStartPre=/bin/sleep 30 to inject a sleep before ExecStart.
Advanced post operations such as increasing the client cache and or configuring the object storage maximum upload and download rates can be achieved with ExecStartPost systemd unit option.