diff options
| author | Nikolay Amiantov <ab@fmap.me> | 2022-01-10 21:30:15 +0300 |
|---|---|---|
| committer | Nikolay Amiantov <ab@fmap.me> | 2022-01-10 22:45:12 +0300 |
| commit | b451eca621d8cd52345e2094e46e970719b6a902 (patch) | |
| tree | a5db3b1261e494dd53606c58950cf3cb34b61780 /pkgs/development/python-modules/rangehttpserver | |
| parent | 0ecf7d414811f831060cf55707c374d54fbb1dec (diff) | |
nscd service: fix ordering and start automatically
During working on #150837 I discovered that `google-oslogin` test
started failing, and so did some of my development machines. Turns out
it was because nscd doesn't start by default; rather it's wanted by
NSS lookup targets, which are not always fired up.
To quote from section on systemd.special(7) on `nss-user-lookup.target`:
> All services which provide parts of the user/group database should be
> ordered before this target, and pull it in.
Following this advice and comparing our unit to official `sssd.service`
unit (which is a similar service), we now pull NSS lookup targets from
the service, while starting it with `multi-user.target`.
Diffstat (limited to 'pkgs/development/python-modules/rangehttpserver')
0 files changed, 0 insertions, 0 deletions