man: emphasize that systemd-userdb-load-credentials.service doesn't do UID/GID allocation

This commit is contained in:
Lennart Poettering
2025-06-02 15:15:33 +02:00
parent c5fcf4ab59
commit a9de5d7d84

View File

@@ -345,16 +345,15 @@
<term><varname>userdb.user.*</varname></term>
<term><varname>userdb.group.*</varname></term>
<listitem>
<para>These credentials should contain valid
<ulink url="https://systemd.io/USER_RECORD">JSON User</ulink> and
<ulink url="https://systemd.io/GROUP_RECORD">JSON Group</ulink> records. For each matching
credential, various files are created in <filename>/etc/userdb/</filename>, implementing the
interface described in
<para>These credentials should contain valid <ulink url="https://systemd.io/USER_RECORD">JSON
User</ulink> and <ulink url="https://systemd.io/GROUP_RECORD">JSON Group</ulink> records. For
each matching credential, various files are created in <filename>/etc/userdb/</filename>,
implementing the interface described in
<citerefentry><refentrytitle>nss-systemd</refentrytitle><manvolnum>8</manvolnum></citerefentry>.
Any passed user records must contain uid and gid fields. Any passed group records must
contain a gid field. For both user and group records, the credential suffix (for
<literal>userdb.user.foobar</literal> the suffix is <literal>foobar</literal>) must match the
user or group name encoded in the record.</para>
Any passed user records must contain valid UID and GID fields. Any passed group records must
contain a GID field (i.e. automatic UID/GID allocation is not supported). For both user and
group records, the credential suffix (for <literal>userdb.user.foobar</literal> the suffix is
<literal>foobar</literal>) must match the user or group name encoded in the record.</para>
<xi:include href="version-info.xml" xpointer="v258"/>
</listitem>