mirror of
https://github.com/systemd/systemd.git
synced 2024-10-30 23:21:22 +03:00
4ced52595f
On distros using Debian's base-passwd, the name of the group with gid 65534 is nogroup. Currently, systemd-sysusers creates a spurious "nobody" group systemd-sysusers[243]: Creating group nobody with gid 996 That's both confusing and redundant, as the nobody user still has primary group 65534 aka nogroup, and the nobody group simply goes completely unused. So explicitly specify the primary group of the nobody user, and add a line ensuring that that group exists. This is not a problem for Debian (or Ubuntu) itself, as they add their own version of basic.conf in their systemd build logic. But it appears on for example Yocto/OpenEmbedded. |
||
|---|---|---|
| .. | ||
| basic.conf.in | ||
| meson.build | ||
| README | ||
| systemd-coredump.conf | ||
| systemd-journal.conf.in | ||
| systemd-network.conf.in | ||
| systemd-oom.conf | ||
| systemd-remote.conf | ||
| systemd-resolve.conf.in | ||
| systemd-timesync.conf.in | ||
Files in this directory contain configuration for systemd-sysusers, a program to allocate system users and groups. See man:sysusers.d(5) for explanation of the configuration file format, and man:systemd-sysusers(8) for a description of when and how this configuration is applied. Use 'systemd-analyze cat-config sysusers.d' to display the effective config.