01.05.2015 02:42, Markus Koschany wrote: > Hello, > > /etc/default/transmission-daemon settings are obsolete if you use > systemd as your default init system. These settings are only valid if > you use the sysV-init system.
Yup. That's exactly what I'm talking about. Valid and supported setup which worked for years breaks once init system changes. It is really trivial to honour the settings in /etc/default/ without breaking existing setups. > 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. 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. Thanks, /mjt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
