You are not logged in.
$ sudo systemctl enable deluged.service
The unit files have no [Install] section. They are not meant to be enabled using systemctl.If this is the case, how then should one go about starting deluged on a system boot?
Offline
This page offers possible solutions in the "Change History" section. Try changing/adding the required .{service,socket} files as you need.
Last edited by alienated_humour (2012-09-29 02:45:50)
Offline
I guess it is because it does not include a WantedBy=multi-user.target... I don't really see how adding that would be detrimental if this is how you were running it before. I assume it just means that you can start/stop it but not enable it on boot.
Edit: corrected systemd terminology.
Last edited by WonderWoofy (2012-09-29 02:48:10)
Offline
Add something like
[Install]
WantedBy=multi-user.targetat the end of deluged.service or however else you want systemd to handle it
Offline
Ah... so it's an upstream issue with the included service/socket files?
Offline
graysky, were you able to fix this?
Offline
graysky, were you able to fix this?
Nope.
Offline
Why not try what crondog suggested? iF it works, submit a patch.
Offline
@tomk - I became too busy with other stuff recently to try this out but I will. Just need some time
I will update the thread with results and will of course take responsibility to open a patch with upstream if successful.
Offline
Add something like
[Install] WantedBy=multi-user.targetat the end of deluged.service or however else you want systemd to handle it
Or just update... Please have a look at https://projects.archlinux.org/svntogit … ges/deluge
Arch Linux is more than just GNU/Linux -- it's an adventure
pkill -9 systemd
Offline