Hi Mark, Mark H Weaver <m...@netris.org> skribis:
> Ludovic Courtès <l...@gnu.org> writes: > >> Last, you’d need to send SIGTSTP to the whole process group of the >> build, like so (I think, haven’t tried): >> >> sudo kill -TSTP -123 >> >> where 123 is the “SessionPID” shown by ‘guix processes’. However, doing >> so may affect build results: processes in the build environment might >> handle SIGTSTP specially, which can have side effects. It’s an >> observable action. > > What's the rationale for using SIGTSTP instead of SIGSTOP here? No good reason; SIGSTOP is safer because it cannot be handled (info "(libc) Job Control Signals"), and thus my argument above is moot. Thanks for the correction! Ludo’.
