Exiting the application leaves transmission-daemon running
I'm not sure if this was caused by the crashes I saw as a result of the #141 (closed) or something else, but I ended up with half-a-dozen instances of transmission-daemon
running.
I believe fragments
should avoid spawning an instance by itself if there's already one running (e.g. due to a crash or perhaps user has set up a systemd service to maingain a daemon)
For a similar reason I feel like fragments
should avoid spawning its own copy of the daemon if fragments is going to connect to a “remote” instance on startup. Users may want to set up fragments to connect to the service daemon by default in which case the instance spawned by fragments
would only interfere.