On 12/14/24 07:43, Max Nikulin wrote:
systemd-analyze verify rsyslog.service
My daily driver, for comparison:
2024-12-14 08:31:02 root@laalaa ~
# cat /etc/debian_version ; uname -a
11.11
Linux laalaa 5.10.0-33-amd64 #1 SMP Debian 5.10.226-1 (2024-10-03)
x86_64 GNU/Linux
2024-12-14 08:31:21 root@laalaa ~
# systemd-analyze verify rsyslog.service
/lib/systemd/system/plymouth-start.service:16: Unit configured to use
KillMode=none. This is unsafe, as it disables systemd's process
lifecycle management for the service. Please update your service to use
a safer KillMode=, such as 'mixed' or 'control-group'. Support for
KillMode=none is deprecated and will eventually be removed.
systemctl status rsyslog.service
2024-12-14 08:32:26 root@laalaa ~
# systemctl status rsyslog.service
* rsyslog.service - System Logging Service
Loaded: loaded (/lib/systemd/system/rsyslog.service; enabled;
vendor preset: enabled)
Active: active (running) since Sat 2024-12-14 07:54:41 PST; 38min ago
TriggeredBy: * syslog.socket
Docs: man:rsyslogd(8)
man:rsyslog.conf(5)
https://www.rsyslog.com/doc/
Main PID: 715 (rsyslogd)
Tasks: 4 (limit: 18973)
Memory: 5.5M
CPU: 56ms
CGroup: /system.slice/rsyslog.service
`-715 /usr/sbin/rsyslogd -n -iNONE
Dec 14 07:54:41 laalaa systemd[1]: Starting System Logging Service...
Dec 14 07:54:41 laalaa rsyslogd[715]: imuxsock: Acquired UNIX socket
'/run/systemd/journal/syslog' (fd 3) from systemd. [v8.2102.0]
Dec 14 07:54:41 laalaa systemd[1]: Started System Logging Service.
Dec 14 07:54:41 laalaa rsyslogd[715]: [origin software="rsyslogd"
swVersion="8.2102.0" x-pid="715" x-info="https://www.rsyslog.com";] start
systemctl --failed
2024-12-14 08:33:36 root@laalaa ~
# systemctl --failed
UNIT LOAD ACTIVE SUB DESCRIPTION
0 loaded units listed.
systemctl --user --failed
2024-12-14 08:35:02 root@laalaa ~
# systemctl --user --failed
UNIT LOAD ACTIVE SUB DESCRIPTION
0 loaded units listed.
david
