diff --git a/man/nss-systemd.xml b/man/nss-systemd.xml
index ff4416c258..ddadef01f5 100644
--- a/man/nss-systemd.xml
+++ b/man/nss-systemd.xml
@@ -108,6 +108,12 @@ lrwxrwxrwx. 1 root root 19 May 10 4711.user-privileged -> foobar.user-privileg
/etc/passwd or /etc/group or other account databases. In fact,
before dropping in these files a reasonable level of care should be taken to avoid user/group name and
UID/GID conflicts.
+
+ The systemd-userdb-load-credentials.service service automatically runs at boot
+ and installs these files from user records passed in via system credentials. See
+ userdbctl1 and
+ systemd.system-credentials7
+ for details.
@@ -186,6 +192,8 @@ vu-rawhide-1000 1637 pts/8 -zsh
systemd-userdbd.service8
systemd-homed.service8
systemd-machined.service8
+ userdbctl1
+ systemd.system-credentials7
nsswitch.conf5
getent1
diff --git a/man/userdbctl.xml b/man/userdbctl.xml
index 77d0b1ffaa..194f8e0e6f 100644
--- a/man/userdbctl.xml
+++ b/man/userdbctl.xml
@@ -42,7 +42,9 @@
url="https://systemd.io/USER_GROUP_API">User/Group Record Lookup API via Varlink, and may also
pick up drop-in JSON user and group records from /etc/userdb/,
/run/userdb/, /run/host/userdb/,
- /usr/lib/userdb/.
+ /usr/lib/userdb/ (see
+ nss-systemd8 for
+ details about drop-in user records).
@@ -343,16 +345,15 @@
userdb.user.*
userdb.group.*
- These credentials should contain valid
- JSON User and
- JSON Group records. For each matching
- credential, various files are created in /etc/userdb/, implementing the
- interface described in
+ These credentials should contain valid JSON
+ User and JSON Group records. For
+ each matching credential, various files are created in /etc/userdb/,
+ implementing the interface described in
nss-systemd8.
- 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
- userdb.user.foobar the suffix is foobar) must match the
- user or group name encoded in the record.
+ 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 userdb.user.foobar the suffix is
+ foobar) must match the user or group name encoded in the record.