Nikolay Amiantov b451eca621 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`.		2022-01-10 22:45:12 +03:00
..
kerberos
cloud-init.nix
dbus.nix
earlyoom.nix	earlyoom module: log stderr to journald	2021-10-05 12:03:24 +01:00
localtime.nix
nscd.conf
nscd.nix	nscd service: fix ordering and start automatically	2022-01-10 22:45:12 +03:00
saslauthd.nix	nixos/doc: clean up defaults and examples	2021-10-04 12:47:20 +02:00
self-deploy.nix
uptimed.nix