Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

transmission-daemon does not launch correctly when using systemd #178

Closed
sandrotosi opened this issue Feb 11, 2017 · 3 comments
Closed

transmission-daemon does not launch correctly when using systemd #178

sandrotosi opened this issue Feb 11, 2017 · 3 comments
Labels
needs clarification More info is needed before work can proceed

Comments

@sandrotosi
Copy link

sandrotosi commented Feb 11, 2017

Hello,
as reported in Debian as http://bugs.debian.org/854856:

it appears the systemd service file for transmission-daemon does not pass a configuration directory when launching the daemon, which will try to use its home directory /home/transmission-daemon, which doesn't exist and cannot be created.

The old init.d file sourced /etc/default/transmission-daemon which defaulted the configuration directory to /var/lib/transmission-daemon/info

could you have a look at this? thanks!

@mikedld
Copy link
Member

mikedld commented Feb 12, 2017

I'm a bit confused. Looking into transmission_2.92-2.debian.tar.xz, and transmission-daemon.postinst in particular, debian-transmission user should have a home directory of "/var/lib/transmission-daemon", not "/home/transmission-daemon".

And then, different distributions use different default configuration directories for the daemon (e.g. Gentoo uses "/var/lib/transmission/config"). How do you propose we fix this?..

@mikedld
Copy link
Member

mikedld commented Jul 5, 2017

Closing for the lack of response.

@mikedld mikedld closed this as completed Jul 5, 2017
@mikedld mikedld added the needs clarification More info is needed before work can proceed label Jul 5, 2017
@Scondo
Copy link

Scondo commented Jan 22, 2018

transmission-daemon.postinst have no way to fix already present transmission-daemon user.

So this will be common bug with update from 2.84 when homedir changed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs clarification More info is needed before work can proceed
Development

No branches or pull requests

3 participants