Gecko [ www.utparral.edu.mx ]

Name	Size	Permission
graphical-session-pre.target.wants	[ DIR ]	drwxr-xr-x
unity-session.target.wants	[ DIR ]	drwxr-xr-x
vte-spawn-.scope.d	[ DIR ]	drwxr-xr-x
at-spi-dbus-bus.service	131 B	-rw-r--r--
dconf.service	161 B	-rw-r--r--
glib-pacrunner.service	147 B	-rw-r--r--
p11-kit-server.service	287 B	-rw-r--r--
p11-kit-server.socket	147 B	-rw-r--r--
pipewire.service	1022 B	-rw-r--r--
pipewire.socket	156 B	-rw-r--r--
session-migration.service	204 B	-rw-r--r--
unity-gtk-module.service	653 B	-rw-r--r--

Code Editor : pipewire.service

[Unit]
Description=PipeWire 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.
#
# A user installing pipewire and doing `systemctl --user 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
ConditionUser=!root

[Service]
LockPersonality=yes
MemoryDenyWriteExecute=yes
NoNewPrivileges=yes
RestrictNamespaces=yes
SystemCallArchitectures=native
SystemCallFilter=@system-service
Type=simple
ExecStart=/usr/bin/pipewire
Restart=on-failure
Slice=session.slice

[Install]
Also=pipewire.socket
WantedBy=default.target

${this.title}

Code Editor : pipewire.service