docs: mention the two other userdb services we ship these days

diff --git a/docs/USER_GROUP_API.md b/docs/USER_GROUP_API.md
index d0016dbc2da19d1556e1afdf82d86efc021a9aeb..15bbfaa0cdbc09f0ad6c8db5b894779b6a7202d5 100644 (file)
--- a/docs/USER_GROUP_API.md
+++ b/docs/USER_GROUP_API.md
@@ -110,7 +110,7 @@ For example, introspection is not available, and the resolver logic is not used.
 
 ## Other Services
 
-The `systemd` project provides three other services implementing this
+The `systemd` project provides several other services implementing this
 interface. Specifically:
 
 1. `io.systemd.DynamicUser` → This service is implemented by the service
@@ -125,6 +125,16 @@ interface. Specifically:
    `systemd-machined.service` and provides records for the users and groups used
    by local containers that use user namespacing.
 
+4. `io.systemd.DropIn` → This service is implemented by
+   `systemd-userdbd.service` and allows storing JSON user records in drop-in
+   files in the `/etc/userdb/`, `/run/userdb/`, `/run/host/userdb/` or
+   `/usr/lib/userdb/` directories.
+
+5. `io.systemd.NamespaceResource` → This service is implemented by
+   `systemd-nsresourced.service` and defines a pair of user and group records
+   for every UID/GID assigned to user namespaces transiently allocated via the
+   service.
+
 Other projects are invited to implement these services too.
 For example, it would make sense for LDAP/ActiveDirectory projects to implement these
 interfaces, which would provide them a way to do per-user resource management