diff options
| author | Arian van Putten <arian.vanputten@gmail.com> | 2021-04-28 19:50:08 +0200 |
|---|---|---|
| committer | ajs124 <git@ajs124.de> | 2021-12-06 14:40:18 +0000 |
| commit | 3efbd53c1b0b6b8c77e11d0382c9b94241a7e6e2 (patch) | |
| tree | 03b48ebb86ff27ebe769e7538ee801cce4e5ed1d /pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch | |
| parent | b4d7911263af4c22ace4a67d50e657fb0cea639d (diff) | |
nixos/systemd: remove nss-{user,}-lookup.target from multi-user.target
There is no real harm having them there; but it means these units really
only become active if there is a service providing the underlying
functionality.
nss-lookup.target should not be pulled in unconditionally. It should be
pulled in by providers of DNS lookups. E.g. systemd-resolved.service has
a Wants=nss-lookup.target, Before=nss-lookup.target. So once
systemd-resolved.service has finished starting up; other units that rely
on DNS can be started; but if systemd-resolved is not enabled; those
units can start up immediately.
Same story goes for nss-user-lookup.target and daemons like sssd.
From https://systemd.io/UIDS-GIDS/:
Note that nss-user-lookup.target is a passive unit: in order to
minimize synchronization points on systems that don’t need it the unit
is pulled into the initial transaction only if there’s at least one
service that really needs it, and that means only if there’s a service
providing the local user database somehow through IPC or suchlike.
Diffstat (limited to 'pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch')
0 files changed, 0 insertions, 0 deletions