| Server IP : 147.93.80.58 / Your IP : 216.73.216.195 Web Server : LiteSpeed System : Linux id-dci-web1866.main-hosting.eu 5.14.0-503.38.1.el9_5.x86_64 #1 SMP PREEMPT_DYNAMIC Fri Apr 18 08:52:10 EDT 2025 x86_64 User : u939086737 ( 939086737) PHP Version : 8.2.28 Disable Function : system, exec, shell_exec, passthru, mysql_list_dbs, ini_alter, dl, symlink, link, chgrp, leak, popen, apache_child_terminate, virtual, mb_send_mail MySQL : OFF | cURL : ON | WGET : ON | Perl : OFF | Python : OFF | Sudo : OFF | Pkexec : OFF Directory : /lib/systemd/user/ |
Upload File : |
[Unit] Description=PipeWire PulseAudio # We require pipewire-pulse.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-pulse` # 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-pulse.socket is not needed, as it is already implicit in the # socket-service relationship, see systemd.socket(5). Requires=pipewire-pulse.socket ConditionUser=!root Wants=pipewire.service pipewire-session-manager.service After=pipewire.service pipewire-session-manager.service Conflicts=pulseaudio.service [Service] LockPersonality=yes MemoryDenyWriteExecute=yes NoNewPrivileges=yes RestrictNamespaces=yes SystemCallArchitectures=native SystemCallFilter=@system-service Type=simple ExecStart=/usr/bin/pipewire-pulse Restart=on-failure Slice=session.slice [Install] Also=pipewire-pulse.socket WantedBy=default.target