SymbX/systemd
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

man: fix description of .membership files

Browse Source 
First, let's say "must" rather than "shall" regarding creation of these
files, because without them group memberships will not work.

Secondly, suggest placing an empty JSON object in them, rather than
making them empty, simply to avoid issues with older systems that didn't
backport d6570eafe3.

Fixes: #38943
This commit is contained in:
Lennart Poettering
2025-10-09 06:32:59 +02:00
parent fd99d9d1cb
commit b97fccf0ce
1 changed files with 6 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
man/nss-systemd.xml
+6 -5
View File
@@ -98,11 +98,12 @@ lrwxrwxrwx. 1 root root 19 May 10 4711.user-privileged -> foobar.user-privileg
users in groups. Specifically, for every pair of user/group where the user shall be a member of a group a users in groups. Specifically, for every pair of user/group where the user shall be a member of a group a
file named file named
<literal><replaceable>username</replaceable>:<replaceable>groupname</replaceable>.membership</literal> <literal><replaceable>username</replaceable>:<replaceable>groupname</replaceable>.membership</literal>
should be created, i.e. the textual UNIX user name, followed by a colon, followed by the textual UNIX must be created, i.e. the textual UNIX user name, followed by a colon, followed by the textual UNIX group
group name, suffixed by <literal>.membership</literal>. The contents of these files are currently not name, suffixed by <literal>.membership</literal>. The contents of these files are currently not read,
read, and the files should be created empty. The mere existence of these files is enough to affect a however it is recommended to create them containing an empty JSON object
user/group membership. If a program provides user and/or group record files in the searched directories, (i.e. <literal>{}</literal>). The mere existence of these files is enough to affect a user/group
it should always also create such files, both for primary and auxiliary group memberships.</para> membership. If a program provides user and/or group record files in the searched directories, it must
always also create such files, both for primary and auxiliary group memberships.</para>
<para>Note that static user/group records generally do not override conflicting records in <para>Note that static user/group records generally do not override conflicting records in
<filename>/etc/passwd</filename> or <filename>/etc/group</filename> or other account databases. In fact, <filename>/etc/passwd</filename> or <filename>/etc/group</filename> or other account databases. In fact,