1[Unit] 2Description=Sound Service 3 4# We require pulseaudio.socket to be active before starting the daemon, because 5# while it is possible to use the service without the socket, it is not clear 6# why it would be desirable. 7# 8# A user installing pulseaudio and doing `systemctl --user start pulseaudio` 9# will not get the socket started, which might be confusing and problematic if 10# the server is to be restarted later on, as the client autospawn feature 11# might kick in. Also, a start of the socket unit will fail, adding to the 12# confusion. 13# 14# After=pulseaudio.socket is not needed, as it is already implicit in the 15# socket-service relationship, see systemd.socket(5). 16Requires=pulseaudio.socket 17ConditionUser=!root 18 19[Service] 20ExecStart=@PA_BINARY@ --daemonize=no --log-target=journal 21LockPersonality=yes 22MemoryDenyWriteExecute=yes 23NoNewPrivileges=yes 24Restart=on-failure 25RestrictNamespaces=yes 26SystemCallArchitectures=native 27SystemCallFilter=@system-service 28# Note that notify will only work if --daemonize=no 29Type=notify 30UMask=0077 31 32[Install] 33Also=pulseaudio.socket 34WantedBy=default.target 35