On 09/29/2018 01:24 AM, Kevin Fenzi wrote: > On 09/26/2018 10:59 PM, Pablo Iranzo Gómez wrote: >> Hi Kevin, >> >> What about using transmission-daemon which is available in Fedora? >> >> (also console with optional Web UI) > > Yeah, we looked at it the last time, but it there were issues... > > I think the daemon version still pulled in the entire gtk stack or you > couldn't > manage it via config files. Looks like it might be better now... I've been successfully using transmission-daemon since January. It can definitely be managed via config files, but it expects to own config files - it overwrites them when the process terminates. This can be worked around easily, eg. by updating config files when the deamon is not running: - name: Create transmission config directory file: dest=/var/lib/transmission/.config/transmission-daemon/ state=directory owner=transmission group=transmission - name: Copy transmission config file template: src=settings.json.j2 dest=/var/lib/transmission/.config/transmission-daemon/settings.json register: settings_j2 - name: Stop transmission-daemon service: name=transmission-daemon state=stopped when: settings_j2.changed - name: Copy transmission config file again template: src=settings.json.j2 dest=/var/lib/transmission/.config/transmission-daemon/settings.json when: settings_j2.changed - name: Start and enable transmission-daemon service: name=transmission-daemon state=started enabled=true -- Mikolaj Izdebski Senior Software Engineer, Red Hat IRC: mizdebsk _______________________________________________ infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
