From e2eaae1155c6eae40751bea53ce671f8aa50dd7f Mon Sep 17 00:00:00 2001 From: Peter Simons Date: Wed, 3 Apr 2013 12:48:25 +0200 Subject: [PATCH] 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 for further details. --- modules/config/networking.nix | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/config/networking.nix b/modules/config/networking.nix index dbf67653dad..272f9271ec1 100644 --- a/modules/config/networking.nix +++ b/modules/config/networking.nix @@ -67,7 +67,7 @@ in '' + optionalString config.services.nscd.enable '' # Invalidate the nscd cache whenever resolv.conf is # 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 '' # only send one DNS request at a time resolv_conf_options='single-request'