On 05.05.2015 11:16, Michael Tokarev wrote:
> 01.05.2015 02:42, Markus Koschany wrote:
[...]
>>     The correct way to modify your settings is
>> to edit /etc/transmission-daemon/settings.json anyway. You can change
>> all desired configuration options there.
> 
> Unfortunately this does not work.  It requires this file to be writable
> by the user transmission-daemon is running as, or else the daemon can't
> save the file.  In particular, new version brings new settings which we'll
> never know about if the daemon can't save this file.
> 
> Making this file writable also requires that whole /etc is writable,
> which makes it impossible to keep root filesystem mounted read-only,
> which is quite common practice especially on systems which faces
> network 24x7.

First of all /etc/transmission/settings.json is a symlink to
/var/lib/transmission-daemon/.config/transmission-daemon/settings.json.
The /etc symlink is only for the user's convenience because system-wide
configuration should be possible in /etc but of course you can always
edit settings.json directly. If you change the file permissions to
read-only and diverge from the default settings, you are still
responsible that services work as expected. This is not a packaging
issue but the core duty of every administrator.

> There was a standard supported way to stop all these problems completely,
> by moving whole home directory including the settings file to alternative
> place, just by giving another value to the daemon (--config-dir option).
> Now it doesn't work anymore, breaking existing setup and making it
> unsupported.
> 
>>   In my opinion
>> this is not a bug but just the way it is intended by upstream.
> 
> Upstream provides --config-dir option for a reason.  Debian package
> had it configurable for ages, and systemd integration already uses
> this option but with a fixed value.  The only tiny step left is to
> connect the two pieces together, this is what I'm talking about.
> 

The old version in wheezy didn't even create a valid home directory but
the new one is now set to /var/lib/transmission-daemon. There you can
change all your configuration options. If you really want to use the
--config-dir option and override the settings you have to create a
custom systemd service file and save it to
/etc/systemd/system/transmission-daemon.service. Just append the
--config-dir option to the ExecStart line, restart the service and it is
done.

I am not the maintainer of transmission, but in my opinion there is
nothing wrong with the packaging of transmission-daemon. If you make
custom changes, you are also responsible for all further configuration.
There is no automatic way to detect all corner cases and it is trivial
to create a custom systemd service file and to adjust it to your needs.

Regards,

Markus



Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to