From 74295866f511a76199e7ab74aa995403c6f40954 Mon Sep 17 00:00:00 2001 From: Eelco Dolstra Date: Sun, 7 Oct 2012 00:37:36 -0400 Subject: [PATCH] Don't include NSS modules in $LD_LIBRARY_PATH This is broken because it requires restarting applications to see new NSS modules. The proper way to handle NSS modules is through nscd. See commit 554ae9908b4abd45c9769da023470ae2c12ebdfd. --- modules/config/nsswitch.nix | 13 ------------- 1 file changed, 13 deletions(-) diff --git a/modules/config/nsswitch.nix b/modules/config/nsswitch.nix index 4c46e8ec87d3..806ff8763038 100644 --- a/modules/config/nsswitch.nix +++ b/modules/config/nsswitch.nix @@ -62,17 +62,4 @@ in # a valid IP address. It returns all locally configured IP # addresses, or ::1 and 127.0.0.2 as fallbacks. system.nssModules = [ pkgs.nss_myhostname ]; - - environment.shellInit = - if config.system.nssModules.path != "" then - '' - LD_LIBRARY_PATH=${config.system.nssModules.path}:$LD_LIBRARY_PATH - '' - else ""; - - # NSS modules need to be in `systemPath' so that (i) the builder - # chroot gets to seem them, and (ii) applications can benefit from - # changes in the list of NSS modules at run-time, without requiring - # a reboot. - environment.systemPackages = [ config.system.nssModules.list ]; }