Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#31723 - [transmission-cli] Add $TRANS_ARGS to the service configuration file

Attached to Project: Arch Linux
Opened by Bruno (gabuzo) - Friday, 28 September 2012, 20:30 GMT
Last edited by Tom Gundersen (tomegun) - Tuesday, 02 October 2012, 09:50 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Ionut Biru (wonder)
Tom Gundersen (tomegun)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
The file transmission.service file does not take in account the $TRANS_ARGS from /etc/conf.d/transmissiond, nor the $TRANS_USER variable.

This is inconsistant with the rc.d behavior.

* package version(s) - 2.61.4

Steps to reproduce:
Add a configuration in /etc/conf.d/transmissiond, restart the daemon, no change applied.
This task depends upon

Closed by  Tom Gundersen (tomegun)
Tuesday, 02 October 2012, 09:50 GMT
Reason for closing:  Won't implement
Comment by Gerardo Exequiel Pozzi (djgera) - Friday, 28 September 2012, 20:38 GMT
Also, Type=forking can be avoided since there is a flag to avoid daemonize (-f | --foreground)
Comment by Tom Gundersen (tomegun) - Monday, 01 October 2012, 14:37 GMT
This was intentional. /etc/conf.d/ is Arch-specific, and any reference to it can not be part of the upstream service file (which will hopefully appear in a future release). Moreover, most (if not all?) of TRANS_ARGS can be configured internally in transmission.

If there are things you wish to tweak which can not be configured internally, make a copy of the service file in /etc/systemd/system/ and edit it there.

@Gerardo: we can not use --foreground as other daemons might (in principle at least) wish to order themselves After=transmission.service. Since transmission is not socket-activated, we need to wait for transmission to finish setting itself up and creating the various sockets before we consider it started. Since that kind of setup happens before the daemon forks, Type=forking gives the right behavior.

Loading...