Eelco Dolstra 1db38ae81b When using chroots, use a private PID namespace ... In a private PID namespace, processes have PIDs that are separate from the rest of the system. The initial child gets PID 1. Processes in the chroot cannot see processes outside of the chroot. This improves isolation between builds. However, processes on the outside can see processes in the chroot and send signals to them (if they have appropriate rights). Since the builder gets PID 1, it serves as the reaper for zombies in the chroot. This might turn out to be a problem. In that case we'll need to have a small PID 1 process that sits in a loop calling wait().		2012-06-25 15:45:16 -04:00
..
bin2c
boost
bsdiff-4.3	Drop the externals directory	2012-03-18 23:54:57 +01:00
libexpr	Use Bison 2.5	2012-04-13 14:28:26 +02:00
libmain	Ensure that Perl processes delete their entry in the temproots directory	2012-03-13 17:07:49 +01:00
libstore	When using chroots, use a private PID namespace	2012-06-25 15:45:16 -04:00
libutil	When using chroots, use a private PID namespace	2012-06-25 15:45:16 -04:00
nix-env	Remove unnecessary "system" argument	2012-04-14 18:48:11 +02:00
nix-hash	* Move parseHash16or32 into libutil, and use in nix-hash.	2011-12-02 11:47:06 +00:00
nix-instantiate	nix-instantiate: default to "default.nix" if no arguments are given	2012-04-17 17:19:43 +02:00
nix-log2xml
nix-setuid-helper
nix-store	"nix-store -l": support compressed logs	2012-05-30 00:00:02 -04:00
nix-worker	Support socket-based, on-demand activation of the Nix daemon with systemd	2012-06-18 23:01:46 -04:00
Makefile.am