问题[systemd](unix)

当我运行hostnamectl命令时，我得到以下输出：

$ hostnamectl 
 Static hostname: myhostname
       Icon name: computer-desktop
         Chassis: desktop 🖥
      Machine ID: 12345e09a3a2464689c345fe7b12345f
         Boot ID: 123451b9f31ff4c166f8368c1f86666ad
Operating System: openSUSE Leap 15.6              
     CPE OS Name: cpe:/o:opensuse:leap:15.6
          Kernel: Linux 6.4.0-150600.23.33-default
    Architecture: x86-64
 Hardware Vendor: ASRock
  Hardware Model: B450 Pro4 R2.0
Firmware Version: P5.60
   Firmware Date: Thu 2022-10-20
    Firmware Age: 2y 5month 2w 3d  <<<<<<<<<< this

我想知道：这个值是Firmware Age从哪里来的？我不知道还有其他命令可以返回这个值。hostnamectl这个值是如何以及从哪里获取的？

我已经创建了一个service文件：

cat ~/.config/systemd/user/rclonegdrive.service 
[Unit]
Description=Rclone mound Google Drive
Wants=network-online.target
After=network-online.target

[Service]
Type=simple
ExecStart=/usr/bin/rclone mount gdrive: /home/rudra/Desktop/Zotero
TimeoutSec=5
Restart=on-failure
RestartSec=1
ExecStop=/usr/bin/fusermount -u /home/rudra/Desktop/Zotero
# logs to the journal directly, suppress double logging

[Install]
WantedBy=default.target

但是，它不能与 systemctl 一起使用：

systemctl --user start rclonegdrive.service
Failed to connect to user scope bus via local transport: Connection refused

这是我的systemd/user内容

tree ~/.config/systemd/user/
/home/rudra/.config/systemd/user/
├── default.target.wants
│   └── [email protected] -> /usr/lib/systemd/user/[email protected]
└── rclonegdrive.service

请问有什么帮助吗？

我正在运行一个备份脚本（rsync 包装器），--log-file之前我在 rsync 中使用了标志，在切换到StandardOutput/StandardError后，systemd 开始在日志行之间附加“ ^M ”。请问我该如何使用单元文件指令将其删除？

[Unit]
Description=...
Wants=...

[Service]
Type=oneshot
User=adrian
Group=adrian
ReadOnlyPaths=/
ReadWritePaths=/var/log/foo.log
StandardOutput=append:/var/log/foo.log
StandardError=append:/var/log/foo.log
ExecPaths=/usr/local/bin /usr/bin /bin
ExecStart=/usr/local/bin/foo_script.sh

[Install]
WantedBy=multi-user.target

环境设置

echo $LANG
en_US.UTF-8

我尝试了多种输出模式，但结果相同。

这不是由编辑器或其他工具引起的，而是 systemd loggin 正在附加它。使用 rsync 标志在脚本中指定日志记录的原始版本工作正常。journalctl -u <service name>渲染正常，但 systemd 输出指令正在将其附加在那里。

我有以下系统：

root@debian:~# dpkg -l systemd-resolved
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name             Version      Architecture Description
+++-================-============-============-=================================
ii  systemd-resolved 257.4-3      amd64        systemd DNS resolver
root@debian:~# cat /etc/issue
Debian GNU/Linux trixie/sid \n \l

root@debian:~# ls -l /etc/resolv.conf
lrwxrwxrwx 1 root root 39 Mar 26 20:21 /etc/resolv.conf -> ../run/systemd/resolve/stub-resolv.conf

root@debian:~# cat /run/systemd/resolve/stub-resolv.conf 
# This is /run/systemd/resolve/stub-resolv.conf managed by man:systemd-resolved(8).
# Do not edit.
#
# This file might be symlinked as /etc/resolv.conf. If you're looking at
# /etc/resolv.conf and seeing this text, you have followed the symlink.
#
# This is a dynamic resolv.conf file for connecting local clients to the
# internal DNS stub resolver of systemd-resolved. This file lists all
# configured search domains.
#
# Run "resolvectl status" to see details about the uplink DNS servers
# currently in use.
#
# Third party programs should typically not access this file directly, but only
# through the symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a
# different way, replace this symlink by a static file or a different symlink.
#
# See man:systemd-resolved.service(8) for details about the supported modes of
# operation for /etc/resolv.conf.

nameserver 127.0.0.53
options edns0 trust-ad
search .

然后我安装了Zebedee隧道，它工作正常。
当我设置firefox开启时localhost:81，我对网站的访问被过滤了。

root@debian:~# telnet localhost 81
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.

现在我想使用 DNS over localhost:81。
我该怎么做？

更新： 我的resolvectl是：

root@debian:~# resolvectl status
Global
         Protocols: +LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported
  resolv.conf mode: stub
       DNS Servers: 8.8.8.8

Link 2 (enp0s31f6)
    Current Scopes: LLMNR/IPv4 mDNS/IPv4
         Protocols: -DefaultRoute +LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported
     Default Route: no

Link 3 (wlp58s0)
    Current Scopes: none
         Protocols: -DefaultRoute +LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported
     Default Route: no

Link 5 (docker0)
    Current Scopes: none
         Protocols: -DefaultRoute +LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported
     Default Route: no

我想知道哪些服务不会随系统启动自动启动，因为PRESET模式是disabled通过systemctl list-unit-files。

两个命令都会产生错误消息：

systemctl list-unit-files --no-pager --preset=disabled

systemctl list-unit-files --no-pager --preset-mode=disabled

错误信息：

Failed to parse preset mode: disabled.

列出缺失的服务

systemctl --state=not-found --all

输出：

      UNIT                           LOAD      ACTIVE   SUB  DESCRIPTION                   
● boot.automount                 not-found inactive dead boot.automount                
● home.mount                     not-found inactive dead home.mount
● tmp.mount                      not-found inactive dead tmp.mount                     
● connman.service                not-found inactive dead connman.service
● console-screen.service         not-found inactive dead console-screen.service
● dpdk.service                   not-found inactive dead dpdk.service
● fcoe.service                   not-found inactive dead fcoe.service
● firewalld.service              not-found inactive dead firewalld.service
● haveged.service                not-found inactive dead haveged.service
● ip6tables.service              not-found inactive dead ip6tables.service
● iptables.service               not-found inactive dead iptables.service
● iscsi-shutdown.service         not-found inactive dead iscsi-shutdown.service
● iscsi.service                  not-found inactive dead iscsi.service
● iscsid.service                 not-found inactive dead iscsid.service
● kbd.service                    not-found inactive dead kbd.service
● rbdmap.service                 not-found inactive dead rbdmap.service
● systemd-hwdb-update.service    not-found inactive dead systemd-hwdb-update.service
● systemd-oomd.service           not-found inactive dead systemd-oomd.service
● systemd-update-done.service    not-found inactive dead systemd-update-done.service
● systemd-vconsole-setup.service not-found inactive dead systemd-vconsole-setup.service
● xencommons.service             not-found inactive dead xencommons.service
● xendomains.service             not-found inactive dead xendomains.service            
● virtlxcd.socket                not-found inactive dead virtlxcd.socket
● virtqemud.socket               not-found inactive dead virtqemud.socket
● virtvboxd.socket               not-found inactive dead virtvboxd.socket
● virtvzd.socket                 not-found inactive dead virtvzd.socket
● virtxend.socket                not-found inactive dead virtxend.socket

查找引用缺失服务的单元

grep -rR "<service_name>" /usr/lib/systemd
grep -rR "<service_name>" /etc/systemd

# See tables in man page for more directories to search with grep and to learn their purpose
man systemd.unit

样品tmp.mount

grep -rR "tmp.mount" /usr/lib/systemd
grep -rR "tmp.mount" /etc/systemd

输出：

/usr/lib/systemd/system/basic.target:After=sysinit.target sockets.target paths.target slices.target tmp.mount
/usr/lib/systemd/system/basic.target:Wants=tmp.mount

清理引用

sudo nano /usr/lib/systemd/system/basic.target

内容：

[Unit]
Description=Basic System
Documentation=man:systemd.special(7)
Requires=sysinit.target
Wants=sockets.target timers.target paths.target slices.target
After=sysinit.target sockets.target paths.target slices.target tmp.mount

RequiresMountsFor=/var /var/tmp
Wants=tmp.mount

在这里我们发现tmp.mount了After=Wants=

我想删除这些条目以便systemctl --state=not-found --all不再列出它，对于每个缺失的单元也是如此。

问题

删除系统上每个缺失单元的此类条目是否安全？

我的一项服务最近因 而停止运行oom-kill。

$ systemctl status my-server.service
● my-server.service - "General purposes load-independent HTTP server"
     Loaded: loaded (/lib/systemd/system/my-server.service; enabled; vendor preset: enabled)
     Active: failed (Result: oom-kill) since Thu 2025-02-27 12:47:44 CST; 17h ago
    Process: 636 ExecStart=/usr/bin/my-server --listen-http :13668 --threads 10 (code=exited, status=0/SUCCESS)
   Main PID: 636 (code=exited, status=0/SUCCESS)
        CPU: 52min 57.893s

Feb 27 12:47:44 ios systemd[1]: my-server.service: A process of this unit has been killed by the OOM killer.
Feb 27 12:47:44 ios my-server[636]: Received signal to stop (15). Stopping...
Feb 27 12:47:44 ios systemd[1]: my-server.service: Failed with result 'oom-kill'.
Feb 27 12:47:44 ios systemd[1]: my-server.service: Consumed 52min 57.893s CPU time.

man systemd.exec当“服务进程被内存不足（OOM）终止程序终止”时，表示$SERVICE_RESULT设置为“服务进程被内存不足（OOM）终止程序终止”。oom-kill

这是 的长期运行子进程中发生的内存泄漏/usr/bin/my-server。发生这种情况时，我希望Restart=服务能够正常运行。

问题：

是否$SERVICE_RESULT=oom-kill触发不干净的退出代码，或者不干净的信号？

我想Restart=尽可能地限制自己。因此，我想oom-kill从以下列表中选择符合条件的第一个条件：

• Restart=on-abort如果它是一个不干净的信号，则可以使用它。
• Restart=on-abormal可以用于上述情况，或者如果它触发超时原因，或看门狗原因（可能不适用）。
• Restart=on-failure适用于上述所有情况，外加不干净的退出代码。
• Restart=always理论上涵盖一切

从man systemd.service：

Table 2. Exit causes and the effect of the Restart= settings
┌──────────────────────┬────┬────────┬────────────┬────────────┬─────────────┬──────────┬─────────────┐
│Restart settings/Exit │ no │ always │ on-success │ on-failure │ on-abnormal │ on-abort │ on-watchdog │
│causes                │    │        │            │            │             │          │             │
├──────────────────────┼────┼────────┼────────────┼────────────┼─────────────┼──────────┼─────────────┤
│Clean exit code or    │    │ X      │ X          │            │             │          │             │
│signal                │    │        │            │            │             │          │             │
├──────────────────────┼────┼────────┼────────────┼────────────┼─────────────┼──────────┼─────────────┤
│Unclean exit code     │    │ X      │            │ X          │             │          │             │
├──────────────────────┼────┼────────┼────────────┼────────────┼─────────────┼──────────┼─────────────┤
│Unclean signal        │    │ X      │            │ X          │ X           │ X        │             │
├──────────────────────┼────┼────────┼────────────┼────────────┼─────────────┼──────────┼─────────────┤
│Timeout               │    │ X      │            │ X          │ X           │          │             │
├──────────────────────┼────┼────────┼────────────┼────────────┼─────────────┼──────────┼─────────────┤
│Watchdog              │    │ X      │            │ X          │ X           │          │ X           │
└──────────────────────┴────┴────────┴────────────┴────────────┴─────────────┴──────────┴─────────────┘

我正在尝试在我的邮件服务器 (Rocky Linux 9.5) 上设置 SpamAssassin。只是一个基本设置！

这是选项变量/etc/sysconfig/spamassassin：

SPAMDOPTIONS="-d -c -m5 -H --create-prefs --max-children 2 -u spamd -g spamd --socketpath=/var/lib/spamassassin/spamd.sock --socketowner=spamd --socketgroup=spamd --socketmode=0666 -s /var/log/spamd.log --debug"

--debug临时添加

当我使用启动SpamAssassin时systemctl，它会因随机错误而退出，并且systemd会再次重新启动它，我将截断的日志放在下面：

.
.
Fri Feb 14 19:59:03 2025 [2133] info: spamd: server successfully spawned child process, pid 2135
Fri Feb 14 19:59:03 2025 [2133] dbg: prefork: child 2135: entering state 0
Fri Feb 14 19:59:03 2025 [2133] dbg: prefork: new lowest idle kid: none
Fri Feb 14 19:59:03 2025 [2135] dbg: spamd: Privilege de-escalation from user 0 and groups 0
Fri Feb 14 19:59:03 2025 [2135] dbg: spamd: setgid ERRNO is 
Fri Feb 14 19:59:03 2025 [2135] dbg: util: get_user_groups: uid is 98
Fri Feb 14 19:59:03 2025 [2133] info: spamd: server successfully spawned child process, pid 2136
Fri Feb 14 19:59:03 2025 [2133] dbg: prefork: child 2136: entering state 0
Fri Feb 14 19:59:03 2025 [2133] dbg: prefork: new lowest idle kid: none
Fri Feb 14 19:59:03 2025 [2136] dbg: spamd: Privilege de-escalation from user 0 and groups 0
Fri Feb 14 19:59:03 2025 [2136] dbg: spamd: setgid ERRNO is 
Fri Feb 14 19:59:03 2025 [2136] dbg: util: get_user_groups: uid is 98
Fri Feb 14 19:59:03 2025 [2133] info: spamd: server killed by SIGTERM, shutting down
Fri Feb 14 19:59:04 2025 [2137] dbg: logger: successfully added file method
.
.

我决定使用以下命令并spamd从cli前台和守护进程运行，它完美地运行！

sudo -u spamd -- spamd -c -m5 -H --create-prefs --max-children 2 -u spamd -g spamd --socketpath=/var/lib/spamassassin/spamd.sock --socketowner=spamd --socketgroup=spamd --socketmode=0666 -s /var/log/spamd.log --debug

sudo即使没有!它也能正常工作。

有人遇到过与 SpamAssassin 或任何其他服务类似的问题吗？

我们获得了三项服务PrivateTmp=yes（tomcat、clamd和soffice）。 clamd并soffice已JoinsNamespaceOf=tomcat.service设置。

clamd应该能够读取tomcat写入它的所有内容/tmp，对吗？

有没有可能（例如重新启动服务）导致此连接在运行时中断（例如clamd失去读取能力tomcat's /tmp）？

我如何在运行时验证该连接是否存在（是否仍然有效）？

我尝试使用lsns和lsns NS来查看任何关系，但无法识别任何东西。

我希望每当我插入某个 USB 设备时，自动启动 GUI 应用程序。启动后，该应用程序在前台运行，不应以 root 身份运行。

我怎样才能做到这一点？

在我的特定情况下，每当我插入 Yubikey USB FIDO2/TOTP 硬件令牌时，我都希望运行Yubico Authenticator 。