Skip to content

Commit f2147ed

Browse files
committed
docs: link info about static user/group drop-in files from the relevant specs
1 parent 62a90b4 commit f2147ed

File tree

2 files changed

+11
-1
lines changed

2 files changed

+11
-1
lines changed

docs/USER_GROUP_API.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -19,6 +19,12 @@ expose. Or in other words, it both allows applications to efficiently query
1919
user/group records from local services, and allows local subsystems to provide
2020
user/group records efficiently to local applications.
2121

22+
The concepts described here define an IPC interface. Alternatively, user/group
23+
records may be dropped in number of drop-in directories as files where they are
24+
picked up in addition to the users/groups defined by this IPC logic. See
25+
[`nss-systemd(8)`](https://www.freedesktop.org/software/systemd/man/nss-systemd.html)
26+
for details.
27+
2228
This simple API only exposes only three method calls, and requires only a small
2329
subset of the Varlink functionality.
2430

docs/USER_RECORD.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -75,7 +75,11 @@ Records](https://systemd.io/GROUP_RECORD) that encapsulate UNIX groups.
7575

7676
JSON User Records may be transferred or written to disk in various protocols
7777
and formats. To inquire about such records defined on the local system use the
78-
[User/Group Lookup API via Varlink](https://systemd.io/USER_GROUP_API).
78+
[User/Group Lookup API via
79+
Varlink](https://systemd.io/USER_GROUP_API). User/group records may also be
80+
dropped in number of drop-in directories as files. See
81+
[`nss-systemd(8)`](https://www.freedesktop.org/software/systemd/man/nss-systemd.html)
82+
for details.
7983

8084
## Why JSON?
8185

0 commit comments

Comments
 (0)