The systemd (systemd-vs-sysVinit-cheatsheet.pdf) way of doing things is at it's core way better, especially structured, than sysvinit (/etc/init.d scripts ) but it still has some issues to work out. Therefore I believe most distributions made the move just a little too soon.
Major pros:
- Dependency resolving between services..
- Loss of flexibility through scripting.
Thing I encountered on my journey:
- A lot of existing torrents (5000+!) needed to be reparsed and have their resume files recreated.
- High memory consumption by Transmission indicates that the process of reparsing these torrents is not done in a linear way. (Tree traversal with all single child nodes is NOT the same as linear.)
- Constant crashing because of high memory consumption leading to out of memory error.
- Swap space/partition not used after upgrade to Jessie. I had to reconfigure swap system for that to activate swap to accommodate high memory usage by Transmission.
- Constant crashing because of service startup timeout. Systemd simply kills the service if it takes to long to start.
- lighttpd as the https proxy for Transmission needs reconfiguration and will not start until Transmission has started.
- Adding TimeoutStartSec=infinity to /etc/systemd/system/multi-user.target.wants/transmission-daemon.service under [Service] did not work.
- Adding TimeoutStartSec=0 to /etc/systemd/system/multi-user.target.wants/transmission-daemon.service under [Service] works.
- Adding Environment=TRANSMISSION_WEB_HOME=/my/path/to/unzipped/shift/files to /etc/systemd/system/multi-user.target.wants/transmission-daemon.service under [Service] to activate the Shift Web UI works.
Good luck!