mirror of
https://gitlab.freedesktop.org/pipewire/pipewire.git
synced 2025-11-05 13:30:02 -05:00
systemd: Add system service and socket
Add system service and socket in addition to the user service and socket. The system service is started as pipewire user and group and clients need to be in the pipewire group to be able to connect.
This commit is contained in:
parent
120090741a
commit
5c52670421
5 changed files with 66 additions and 1 deletions
27
src/daemon/systemd/system/pipewire.service.in
Normal file
27
src/daemon/systemd/system/pipewire.service.in
Normal file
|
|
@ -0,0 +1,27 @@
|
|||
[Unit]
|
||||
Description=Multimedia Service
|
||||
|
||||
# We require pipewire.socket to be active before starting the daemon, because
|
||||
# while it is possible to use the service without the socket, it is not clear
|
||||
# why it would be desirable.
|
||||
#
|
||||
# Installing pipewire and doing `systemctl start pipewire` 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. Also, a
|
||||
# start of the socket unit will fail, adding to the confusion.
|
||||
#
|
||||
# After=pipewire.socket is not needed, as it is already implicit in the
|
||||
# socket-service relationship, see systemd.socket(5).
|
||||
Requires=pipewire.socket
|
||||
|
||||
[Service]
|
||||
Type=simple
|
||||
ExecStart=@PW_BINARY@
|
||||
Restart=on-failure
|
||||
RuntimeDirectory=pipewire
|
||||
User=pipewire
|
||||
Environment=PIPEWIRE_RUNTIME_DIR=%t/pipewire
|
||||
|
||||
[Install]
|
||||
Also=pipewire.socket
|
||||
WantedBy=default.target
|
||||
Loading…
Add table
Add a link
Reference in a new issue