Well, what i meant to say is the following. If we for example take your deluged service file. I edited to show it should be.
Code: Select all
fred44nl@Debian:~$ sudo cat /etc/systemd/system/deluged.service
[Unit]
Description=Deluge Bittorrent Client Daemon
Documentation=man:deluged
After=network-online.target
[Service]
Type=simple
User=debian-deluged
Group=community
UMask=002
ExecStart=/usr/bin/deluged -d
Restart=on-failure
# Time to wait before forcefully stopped.
TimeoutStopSec=300
[Install]
WantedBy=multi-user.target
- You create a new group (in this example it is called community. You can off course choose a different name)
groupadd community
- In the systemd unit file (deluged.service) see above, you use this group to be used
- You add your user to this group.
usermod -aG community fred44nl
To see if the user is part of the group, type the following command.
groups fred44nl
- If in the future there is a user called mark and he also needs to have the same access as fred44nl, then you simply add him to that community group. So this way you also make sure you made your configuration flexible for the future if the situation might change with new users. Always try to think ahead, this saves a lot of headaches..speaking from experience
- The umask setting how it was, in your first post was dirty beyond words (000)...how you had in your systemd unit file as that translates to 777 (which means everybody that has an account on your system can delete all those files that have been created by deluge. Ambipro pointed this out, by advising to use 002 (which translates 775)(which means in normal language, owner can do everything, group can do everything, other (everyone else) can just read). But if you did it on purpose of having 777, that defeats the purpose of having your user to be used in the systemd unit file as you can do exactly the same through other bit.
For you, but also for other readers, i would strongly advice to try to understand Linux file permissions. Often people don't understand them, as they don't take the time to understand them...(yes i was also one of those people and yes i back in the day also used 777 until i took the time, so i am not pointing fingers
).
https://linuxize.com/post/understanding ... rmissions/
Doing this, just fixes your problem.
About ACL's, don't. ACL's have their place to be used, but that is in MAYBE less than 5% percent of the cases? If not less. I am saying this as i work in the Linux and Open Source world. I ONLY implemented this once with a customers environment as there was no other way. Only once of all those years.
Deluge
