aboutsummaryrefslogtreecommitdiff
path: root/src/libmain/nix-main.pc.in
diff options
context:
space:
mode:
authorMaximilian Bosch <maximilian@mbosch.me>2023-01-22 22:37:50 +0100
committerMaximilian Bosch <maximilian@mbosch.me>2024-04-26 19:04:06 +0200
commit104448e75d87d03d2fb0b4ac96d4da72e1dae50d (patch)
tree6c73af980f5845cdd003217d200e184eda8cac07 /src/libmain/nix-main.pc.in
parent111db8b38fd8350d92d72fa17fd3d9e8ef5a0e09 (diff)
ssh-ng: Set log-fd for ssh to `4` by default
That's expected by `build-remote` and makes sure that errors are correctly forwarded to the user. For instance, let's say that the host-key of `example.org` is unknown and nix-build ../nixpkgs -A hello -j0 --builders 'ssh-ng://example.org' is issued, then you get the following output: cannot build on 'ssh-ng://example.org?&': error: failed to start SSH connection to 'example.org' Failed to find a machine for remote build! derivation: yh46gakxq3kchrbihwxvpn5bmadcw90b-hello-2.12.1.drv required (system, features): (x86_64-linux, []) 2 available machines: [...] The relevant information (`Host key verification failed`) ends up in the daemon's log, but that's not very obvious considering that the daemon isn't very chatty normally. This can be fixed - the same way as its done for legacy-ssh - by passing fd 4 to the SSH wrapper. Now you'd get the following error: cannot build on 'ssh-ng://example.org': error: failed to start SSH connection to 'example.org': Host key verification failed. Failed to find a machine for remote build! [...] ...and now it's clear what's wrong. Please note that this is won't end up in the derivation's log. For previous discussion about this change see https://github.com/NixOS/nix/pull/7659. Change-Id: I5790856dbf58e53ea3e63238b015ea06c347cf92
Diffstat (limited to 'src/libmain/nix-main.pc.in')
0 files changed, 0 insertions, 0 deletions