pulseaudio/src/daemon/systemd/user/pulseaudio.service.in

[Unit]
Description=Sound Service
Requires=pulseaudio.socket
After=pulseaudio.socket

[Service]
# Note that notify will only work if --daemonize=no
Type=notify
ExecStart=@PA_BINARY@ --daemonize=no
Restart=on-failure

[Install]
Also=pulseaudio.socket
WantedBy=default.target
launch: Add systemd units for launching pulseaudio user instances 2014-10-17 15:10:14 +02:00			`[Unit]`
			`Description=Sound Service`
launch: make pulseaudio.service properly order and require the socket This commit fixes two problems: 1. Because there are no implicit dependencies between sockets and services, the socket, as set up by systemd will race with the socket, as set up by the pulseaudio daemon. This can cause the pulseaudio.socket unit to fail (even though the pulseaudio service started just fine), which can confuse users. 2. While it is possible to use the service without the socket, it is not clear why it would be desirable. And a user installing pulseaudio and doing `systemctl --user start pulseaudio` will not get the socket started, which might be confusing and problematic if the server is to be restarted later on, as the client autospawn feature might kick in. 2016-07-20 09:57:13 -04:00			`Requires=pulseaudio.socket`
			`After=pulseaudio.socket`
launch: Add systemd units for launching pulseaudio user instances 2014-10-17 15:10:14 +02:00
			`[Service]`
daemon: Use Type=notify for systemd service This ensures systemd knows when pulseaudio finishes loading, thus never marking pulseaudio as active if startup fails. 2015-08-13 19:58:27 -03:00			`# Note that notify will only work if --daemonize=no`
			`Type=notify`
launch: Add systemd units for launching pulseaudio user instances 2014-10-17 15:10:14 +02:00			`ExecStart=@PA_BINARY@ --daemonize=no`
			`Restart=on-failure`

			`[Install]`
			`Also=pulseaudio.socket`
			`WantedBy=default.target`