Eelco Dolstra a5c6347ff0 build-remote.pl: Use ‘nix-store --serve’ on the remote side ... This makes things more efficient (we don't need to use an SSH master connection, and we only start a single remote process) and gets rid of locking issues (the remote nix-store process will keep inputs and outputs locked as long as they're needed). It also makes it more or less secure to connect directly to the root account on the build machine, using a forced command (e.g. ‘command="nix-store --serve --write"’). This bypasses the Nix daemon and is therefore more efficient. Also, don't call nix-store to import the output paths.		2014-07-11 16:22:24 +02:00
..
dotgraph.cc	Comment out dead code in `nix-store'.	2010-05-31 16:36:20 +00:00
dotgraph.hh	Use "#pragma once" to prevent repeated header file inclusion	2012-07-18 14:59:03 -04:00
local.mk	nix-store -l: Fetch build logs from the Internet	2014-05-21 17:19:36 +02:00
nix-store.cc	build-remote.pl: Use ‘nix-store --serve’ on the remote side	2014-07-11 16:22:24 +02:00
serve-protocol.hh	build-remote.pl: Use ‘nix-store --serve’ on the remote side	2014-07-11 16:22:24 +02:00
xmlgraph.cc	Add XML output to `nix-store'.	2010-05-31 16:36:24 +00:00
xmlgraph.hh	Use "#pragma once" to prevent repeated header file inclusion	2012-07-18 14:59:03 -04:00