Let resolvconf 'restart' the nscd service instead of 'reload'ing it.

Sometimes nscd starts up before a /etc/resolv.conf file has been written, and
apparently triggering a cache flush (reload) is not good enough to make it
recover from that problem. To remedy the issue, we restart the service instead.
See <https://github.com/NixOS/nixos/issues/34> for further details.
This commit is contained in:
Peter Simons 2013-04-03 12:48:25 +02:00
parent cf3ef6a1fc
commit e2eaae1155

View File

@ -67,7 +67,7 @@ in
'' + optionalString config.services.nscd.enable '' '' + optionalString config.services.nscd.enable ''
# Invalidate the nscd cache whenever resolv.conf is # Invalidate the nscd cache whenever resolv.conf is
# regenerated. # regenerated.
libc_restart='${pkgs.systemd}/bin/systemctl reload --no-block nscd.service' libc_restart='${pkgs.systemd}/bin/systemctl restart --no-block nscd.service'
'' + optionalString cfg.dnsSingleRequest '' '' + optionalString cfg.dnsSingleRequest ''
# only send one DNS request at a time # only send one DNS request at a time
resolv_conf_options='single-request' resolv_conf_options='single-request'