nss-systemd 是一个 glibc(GNU C Library) NSS(Name Service Switch) 插件, 它为单元文件中使用 DynamicUser= 选项动态生成的 UNIX 用户与组 提供了名称解析功能。详见 systemd.exec(5) 手册。 此模块会确保永远能够解析名为"root"与"nobody"的用户与组(也就是 UID/GID 为 0 与 65534 的用户与组), 即使...
So perhaps the nm-online failed to contact the session dbus-daemon (although it seems to work most of the time) and started a new dbus-daemon, which didn't like the environment it was in and passed incorrect things to libnss-systemd? … Member keszybz commented Jul 22, 2020 It is p...
Live Systems Maintainers, libnss-systemd recently changed Priority from optional to standard:https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914876Thus, I believe that live-task-standard should depend on it too. Patch below. Thank you! Dan --- diff -ru a/debian/control b/debian/control ...
Anyway, I don't think we should change systemd in this regard now. We should add some docs around this however, and leave it to downstreams to figure whether they want to patch out the sandboxing again. That said, I am pretty sure in the interest of security for the many the nss_lda...
libnss-systemd に関するリンク Ubuntu の資源: バグ報告 Ubuntu での変更履歴 著作権ファイル systemdソースパッケージをダウンロード: [systemd_256.5-2ubuntu3.dsc] [systemd_256.5.orig.tar.gz] [systemd_256.5-2ubuntu3.debian.tar.xz]
Running unbound 1.11.0 (pkg) on arch linux. Other services rely on nss-lookup.target being reached when name resolution is actually working. To demonstrate the issue I've created the following "check-name-resolution.service": [Unit] Desc...
systemd version the issue has been seen with 0.39.0.0 255.10 Used distribution No response Linux kernel version used No response CPU architectures issue was seen on x86_64 Component systemd-resolved Expected behaviour you didn't see No r...
systemd version the issue has been seen with 256~rc4 Used distribution Debian trixie/sid Linux kernel version used 6.7.12-amd64 CPU architectures issue was seen on x86_64 Component nss-resolve Expected behaviour you didn't see Behaviour when using dns in /etc/nsswitch.conf: % getent hosts ...