3 commits

Author	SHA1	Message	Date
David Runge	1cc492fdb5	Set the systemd unit target to default.target ... fluidsynth.service.in: The [Install] section [1] in systemd unit declares in which target the service will be started. The `multi-user.target` [2] - managed by the systemd _system_ service manager - is used in the `fluidsynth.service`. However, as it is a _user_ unit it needs to be pulled in by the `default.target` [3] instead, which is the main target for the user session (as started by `user@.service` [4]). [1] https://www.freedesktop.org/software/systemd/man/systemd.unit.html#%5BInstall%5D%20Section%20Options [2] https://www.freedesktop.org/software/systemd/man/systemd.special.html#multi-user.target [3] https://www.freedesktop.org/software/systemd/man/systemd.special.html#default.target1 [4] https://www.freedesktop.org/software/systemd/man/user@.service.html	2020-09-22 16:53:20 +02:00
Florian Léger	099369f8b7	Improve systemd integration ... When fluidsynth is run as a service using systemd, make sure the service is considered started only when it is ready to process events. In order to do so: - Add an optional runtime dependency to libsystemd to the fluidsynth executable - Change the systemd service type to "notify" - Have fluidsynth notify systemd that the service is started after the server is started - Have fluidsynth notify systemd that the service is stopping after joining the server thread	2019-03-02 10:18:32 +01:00
derselbst	aa3703b2e3	add systemd service files ... to enable running fluidsynth as user service. Fixes #342	2018-02-20 21:31:35 +01:00