Age | Commit message (Collapse) | Author | Files | Lines | |
---|---|---|---|---|---|
2014-07-24 | Implement nix-copy-closure --from via nix-store --serve | Eelco Dolstra | 1 | -0/+1 | |
2014-07-11 | build-remote.pl: Use ‘nix-store --serve’ on the remote side | Eelco Dolstra | 1 | -0/+2 | |
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-10 | nix-copy-closure: Fix race condition | Eelco Dolstra | 1 | -10/+5 | |
There is a long-standing race condition when copying a closure to a remote machine, particularly affecting build-remote.pl: the client first asks the remote machine which paths it already has, then copies over the missing paths. If the garbage collector kicks in on the remote machine between the first and second step, the already-present paths may be deleted. The missing paths may then refer to deleted paths, causing nix-copy-closure to fail. The client now performs both steps using a single remote Nix call (using ‘nix-store --serve’), locking all paths in the closure while querying. I changed the --serve protocol a bit (getting rid of QueryCommand), so this breaks the SSH substituter from older versions. But it was marked experimental anyway. Fixes #141. | |||||
2014-02-10 | nix-store --serve: Use a versioned protocol | Shea Levy | 1 | -0/+24 | |
Signed-off-by: Shea Levy <shea@shealevy.com> |