Description:

systemd unit drop-ins in /usr/lib/systemd/system and drop-ins in /etc/systemd/system are both read at the same time in alphabetical order. This means that using "systemctl edit deluged.service", which creates "override.conf", doesn't allow the admin to overwrite settings from the deluge-provided "/usr/lib/systemd/system/deluged.service.d/user.conf" as "user.conf" sorts alphabetically after "override.conf".

See https://github.com/systemd/systemd/issues/13198 if you don't believe me.

It sure is possible to override stuff from the deluge-provided "user.conf" by creating your own "user.conf" drop-in or any other name sorting after "user.conf" in "/etc/systemd/system", but I'd wager most admins aren't aware that "systemctl edit…" doesn't guarantee your settings are actually applied.

This has bitten me lately as I had an "override.conf" for a long time changing the service user, and after one of the latest updates this stopped working — due to the deluge-provided "user.conf".

It would be easier for admins if the deluge package used different names for the drop-ins which sort before override.conf alphabetically, e.g. "00user.conf".

It would also be much less surprising.

Same for "deluge-web.service.d/user.conf", of course.

Thanks for considering it!

Additional info:
* package version: 2.0.3-1