aboutsummaryrefslogtreecommitdiff
path: root/src/legacy/nix-collect-garbage.hh
diff options
context:
space:
mode:
authorMaximilian Bosch <maximilian@mbosch.me>2024-10-12 23:42:59 +0200
committerMaximilian Bosch <maximilian@mbosch.me>2024-10-14 06:01:18 +0000
commit4682e40183b86972e5a1ef8f17e5366b9b3a8b2c (patch)
treeff9fd4814236884808699f2cc422c9bca75d58f3 /src/legacy/nix-collect-garbage.hh
parent326cbecb61d42ce73caa391cdcb21acb2581bf7c (diff)
ssh-ng: better way to keep SSH errors visible
A better fix than in 104448e75d87d03d2fb0b4ac96d4da72e1dae50d, hence a revert + the fix. It turns out that this commit has the side-effect that when having e.g. `StrictHostKeyChecking=accept-new` for a remote builder, the warnings à la Warning: Permanently added 'builder' (ED25519) to the list of known hosts. actually end up in the derivation's log whereas hostkey verification errors don't, but only in the stderr of the `nix-build` invocation (which was the motivation for the patch). This change writes the stderr from the build-hook to * the daemon's stderr, so that the SSH errors appear in the journal (which was the case before 104448e75d87d03d2fb0b4ac96d4da72e1dae50d) * the client's stderr, as a log message * NOT to the drv log (this is handled via `handleJSONLogMessage`) I tried to fix the issue for legacy-ssh as well, but failed and ultimately decided to not bother. I know that we'll sooner or later replace the entire component, however this is the part of the patch I have working for a while, so I figured I might still submit it for the time being. Change-Id: I21ca1aa0d8ae281d2eacddf26e0aa825272707e5
Diffstat (limited to 'src/legacy/nix-collect-garbage.hh')
0 files changed, 0 insertions, 0 deletions