summaryrefslogtreecommitdiff
path: root/sysusers.d
diff options
context:
space:
mode:
authorRasmus Villemoes <rasmus.villemoes@prevas.dk>2021-11-30 12:50:19 +0100
committerZbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>2021-11-30 16:16:25 +0100
commit4ced52595f3e0367a0f2823be8b7acf6d7b7c2be (patch)
tree8834e12a4290794e51b90a6af160bcc0f34a6e53 /sysusers.d
parent3d170ca5809639b0ca43b2014a9f745df4b32926 (diff)
downloadsystemd-4ced52595f3e0367a0f2823be8b7acf6d7b7c2be.tar.gz
sysusers: avoid creating spurious "nobody" group
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.
Diffstat (limited to 'sysusers.d')
-rw-r--r--sysusers.d/basic.conf.in5
1 files changed, 3 insertions, 2 deletions
diff --git a/sysusers.d/basic.conf.in b/sysusers.d/basic.conf.in
index 8cc1a7cad2..7f1d052deb 100644
--- a/sysusers.d/basic.conf.in
+++ b/sysusers.d/basic.conf.in
@@ -8,8 +8,9 @@
# The superuser
u root 0 "Super User" /root
-# The nobody user for NFS file systems
-u {{NOBODY_USER_NAME}} 65534 "Nobody" -
+# The nobody user/group for NFS file systems
+g {{NOBODY_GROUP_NAME}} 65534 - -
+u {{NOBODY_USER_NAME }} 65534:65534 "Nobody" -
# Administrator group: can *see* more than normal users
g adm {{ADM_GID }} - -