Tul xxx Tul
User / IP
:
216.73.216.146
Host / Server
:
45.84.207.204 / aircan.me
System
:
Linux lt-bnk-web1726.main-hosting.eu 5.14.0-611.36.1.el9_7.x86_64 #1 SMP PREEMPT_DYNAMIC Tue Mar 3 11:23:52 EST 2026 x86_64
Command
|
Upload
|
Create
Mass Deface
|
Jumping
|
Symlink
|
Reverse Shell
Ping
|
Port Scan
|
DNS Lookup
|
Whois
|
Header
|
cURL
:
/
lib
/
systemd
/
user
/
Viewing: pipewire-pulse.service
[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
Coded With 💗 by
0x6ick