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.

diff --git a/sysusers.d/basic.conf.in b/sysusers.d/basic.conf.in
index 8cc1a7cad218fc9ca1f977dca8749bdcb7a771bd..7f1d052deb7ee48ed1e44dd1757dfdd2edcdc982 100644 (file)
--- 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    }}     -            -