mirrors/pipewire
1
0
Fork 0
mirror of https://gitlab.freedesktop.org/pipewire/pipewire.git synced 2025-10-31 22:25:38 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions

systemd: add PipeWire to the systemd service file descriptions

Browse source 
Without this, a journal entry merely looks like this:
 Stopping Multimedia Service ...

Which is obviously terrible from a branding perspective but also makes
it harder for users to figure out what process was responsible for this
entry.
This commit is contained in:
Peter Hutterer 2021-09-29 14:14:46 +10:00 • committed by Wim Taymans
parent 7c28b0d7af
commit 90cbcb6c05
4 changed files with 4 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

2
src/daemon/systemd/system/pipewire-media-session.service.in
View file

@ -1,5 +1,5 @@
[Unit] [Unit]
Description=Multimedia Service Session Manager Description=PipeWire Media Session Manager
After=pipewire.service After=pipewire.service
BindsTo=pipewire.service BindsTo=pipewire.service

2
src/daemon/systemd/system/pipewire.service.in
View file

@ -1,5 +1,5 @@
[Unit] [Unit]
Description=Multimedia Service Description=PipeWire Multimedia Service
# We require pipewire.socket to be active before starting the daemon, because # 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 # while it is possible to use the service without the socket, it is not clear

2
src/daemon/systemd/user/pipewire-media-session.service.in
View file

@ -1,5 +1,5 @@
[Unit] [Unit]
Description=Multimedia Service Session Manager Description=PipeWire Media Session Manager
After=pipewire.service After=pipewire.service
BindsTo=pipewire.service BindsTo=pipewire.service

2
src/daemon/systemd/user/pipewire.service.in
View file

@ -1,5 +1,5 @@
[Unit] [Unit]
Description=Multimedia Service Description=PipeWire Multimedia Service
# We require pipewire.socket to be active before starting the daemon, because # 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 # while it is possible to use the service without the socket, it is not clear