#can someone check me on how SIGINT works
1 messages · Page 1 of 1 (latest)
iirc when you Ctrl+C in your shell it actually sends it to the entire progress group. So if you run e.g. a | b | c, they'll all receive it, and I guess that includes child processes, but not 100% sure. You can probably shield a child process by giving it a new progress group (SysProcAttr{Setpgid: true})
hehe i was not actually familiar with process groups and this behavior!
thanks, that's helpful
i wonder, would we want something like this behavior for the session in general? should the SDKs detach them?
since we have the stdin trick to close them, the session should manage to close itself even if the client is badly behaved and doesn't shut it down nicely
woops missed this - that seems like a reasonable thing to do yeah, though with Zenith the outermost dagger CLI is what runs the session anyway. I dunno if I'd go as far as to codify this across SDKs, and it's also platform-specific, so meh, a bit of a wash