Changes between Version 18 and Version 19 of UserGuide/Service/systemd

Timestamp:

06/18/2019 08:22:44 AM (5 years ago)

Author:

Cas

Comment:

--

UserGuide/Service/systemd

@@ -1 @@
-= systemd Scripts =
-
-'''Note:''' Improvements to propagate from [wiki:UserGuide/Service/Upstart/ Upstart] still: deluge-web starting upon deluged starting and filesystems are mounted e.g. `local-fs.target` and `remote-fs.target`.
-
-
-== Verify Deluge Installion ==
-
-Ensure Deluge daemon `deluged` and Web UI `deluge-web` are [wiki:Installing/Linux installed]. 
-
-Use `which deluged` or `which deluge-web` to check installation path. 
-
-If they are not installed in the usual `/usr/bin` modify the service file ExecStart lines to point to the correct location (e.g. `/usr/local/bin/deluged`).
-
-== User Management ==
-
-For security it is best to run a service with a specific user and group. You can create one using the following command:
-
-{{{
-sudo adduser --system  --gecos "Deluge Service" --disabled-password --group --home /var/lib/deluge deluge
-}}}
-
- * This creates a new system user and group named `deluge` with no login access and home directory: `/var/lib/deluge`
-
-Add to the `deluge` group any users you wish to be able to easily manage or access files downloaded through Deluge, for example:
-
-{{{
-sudo adduser <username> deluge
-}}}
-
-
-== Migration from init.d or Upstart scripts ==
-Remove any old init.d files named deluge in `/etc/init.d/` like this:
-{{{
-sudo /etc/init.d/deluge-daemon stop
-sudo rm /etc/init.d/deluge-daemon
-sudo update-rc.d deluge-daemon remove
-}}}
-
-Remove old upstart scripts like this:
-{{{
-sudo stop deluged
-sudo stop deluge-web
-sudo rm /etc/init/deluge-web.conf
-sudo rm /etc/init/deluged.conf
-}}}
-
-== Deluge Daemon (deluged) Service ==
-Create the file `/etc/systemd/system/deluged.service` containing the following:
-
-[[Include(http://git.deluge-torrent.org/deluge/plain/packaging/systemd/deluged.service?h=develop, text/plain)]]
-
-
- * You may wish to modify the above `umask` as it applies to any files downloaded by deluged.
-  * 007 grants full access to the user and members of the group deluged is running as (in this case deluge) and prevents access from all other accounts.
-  * 022 grants full access to the user deluged is running as and only read access to other accounts.
-  * 002 grants full access to the user and group deluged is running as and only read access to other accounts.
-  * 000 grants full access to all accounts.
- Refer to [http://en.wikipedia.org/wiki/Umask#Octal_umasks Wikipedia] for details of possible values and their effects. Deluged must be stopped and started instead of just restarted after changes. If you enable logging, as described later in this page, the umasks specified here also affect the permissions of newly created logs.
-
-Now enable it to start up on boot, start the service and verify it is running:
-{{{
-sudo systemctl enable /etc/systemd/system/deluged.service
-sudo systemctl start deluged
-sudo systemctl status deluged
-}}}
-
-== Deluge Web UI (deluge-web) Service ==
-
-Create the file `/etc/systemd/system/deluge-web.service` containing the following:
-{{{
-#!comment
-Don't link develop web service until 2.0 is released
-[[Include(http://git.deluge-torrent.org/deluge/plain/packaging/systemd/deluge-web.service?h=develop, text/plain)]]
-}}}
-
-{{{
-[Unit]
-Description=Deluge Bittorrent Client Web Interface
-Documentation=man:deluge-web
-After=network-online.target deluged.service
-Wants=deluged.service
-[Service]
-Type=simple
-User=deluge
-Group=deluge
-UMask=027
-# This 5 second delay is necessary on some systems
-# to ensure deluged has been fully started
-ExecStartPre=/bin/sleep 5
-ExecStart=/usr/bin/deluge-web
-Restart=on-failure
-[Install]
-WantedBy=multi-user.target
-}}}
-
-Now enable it to start up on boot, start the service and verify it is running:
-{{{
-sudo systemctl enable /etc/systemd/system/deluge-web.service
-sudo systemctl start deluge-web
-sudo systemctl status deluge-web
-}}}
-
-== Logging ==
-Create a log directory for Deluge and give the service user (e.g. `deluge`), full access:
-{{{
-sudo mkdir -p /var/log/deluge
-sudo chown -R deluge:deluge /var/log/deluge
-sudo chmod -R 750 /var/log/deluge
-}}}
- * The deluge log directory is now configured so that user `deluge` has full access, group `deluge` read only and everyone else denied access. The `umask` specified in the services sets the permission of new log files.
-
-Enable logging in the service files by editing the `ExecStart` line, appending `-l` and `-L` options:
-{{{
-ExecStart=/usr/bin/deluged -d -l /var/log/deluge/daemon.log -L warning
-}}}
-{{{
-ExecStart=/usr/bin/deluge-web -l /var/log/deluge/web.log -L warning
-}}} 
- * See [wiki:Troubleshooting#EnableDelugeLogging Deluge Logging] for all available log-levels.
-
-Restart the services:
-{{{
-sudo systemctl daemon-reload
-sudo systemctl restart deluged
-sudo systemctl restart deluge-web
-}}}
-
-=== Log Rotation ===
-To enable log rotation create `/etc/logrotate.d/deluge` with the following code:
-{{{
-/var/log/deluge/*.log {
-        rotate 4
-        weekly
-        missingok
-        notifempty
-        compress
-        delaycompress
-        sharedscripts
-        postrotate
-                systemctl restart deluged >/dev/null 2>&1 || true
-                systemctl restart deluge-web >/dev/null 2>&1 || true
-        endscript
-}
-}}}
-
-== Start `deluged` only if mount exists ==
-Use this if you have a usb disk drive or network drive that may not be immediately available on boot or disconnected at random.
-
-The following additions wait for those mountpoints before starting `deluged`. If they are unmounted or disconnected then `deluged` is stopped. When they become available again `deluged` is started.
-
-Ensure you have added the correct drive details to `fstab` or equivalent so they are mounted at boot.
-
-List the available drive mounts:
-{{{
-sudo systemctl -t mount
-}}}
-
-Look for your mount point in the Description column. Mounts are formatted similar to the mount point with - substituted for / in the path. Eg: `media-xyz.mount`
-
-Modify the `[Unit]` section of the `deluged.service` script. Substitute `xyz.mount` for the mount you want the service to depend on:
-{{{
-[Unit]
-Description=Deluge Bittorrent Client Daemon
-# Start after network and specified mounts are available.
-After=network-online.target xyz.mount
-Requires=xyz.mount
-# Stops deluged if mount points disconnect
-BindsTo=xyz.mount
-}}}
-
-For multiple mount points add a space between additional entries. Eg: `After=network-online.target xyz.mount abc.mount def.mount`
-
-Modify the `[Install]` section to ensure the deluged service is started when the mount point comes back online:
-{{{
-[Install]
-WantedBy=multi-user.target xyz.mount
-}}}
-Note: `WantedBy` seems to work on some distros and not others. Possibly different versions of systemd?
-
-Reference: [https://www.freedesktop.org/software/systemd/man/systemd.unit.html#RequiresMountsFor= systemd.unit]
+Moved to: https://deluge.readthedocs.io/en/latest/how-to/systemd-service.html