Re: RFC: subcommand to pause/resume builds

[Ludovic Courtès]

Hi,

John Soo <jsoo1@asu.edu> skribis:

> This feels close to little sed/awk pipelines.  Which is not to be
> entirely dismissive. I like the compositionality of these tools.  In
> fact I mentioned earlier that it might be good to send arbitrary
> signals. But why not let kill (shell or scheme) do that?  All we would
> need is to filter and format pids in a composable way (on the scheme
> side and the shell side). That has the benefits of remaining agnostic on
> side effects in builds (let the user decide what they are comfortable
> with) and being more composable.
>
> Maybe flags like this would be enough:
>
> guix processes --session=<derivation-regex> ...
>
> to get something like
>
> 5555
> 1212
> 343434
> ...

You can filter by piping ‘guix processes’ output through ‘recsel’:

--8<---------------cut here---------------start------------->8---
$ sudo guix processes | recsel -p SessionPID,LockHeld -e 'LockHeld ~ "chromium"'
SessionPID: 31410
LockHeld: 
/gnu/store/kdsp1pjj6znaxzs3d0vfwdcddc436g7f-ungoogled-chromium-86.0.4240.183-0.b68e17f.lock

SessionPID: 3455
LockHeld: 
/gnu/store/bhy3c5damrpzx7hdp8bam1lk2rk7789r-ungoogled-chromium-86.0.4240.183-0.b68e17f.lock
--8<---------------cut here---------------end--------------->8---

HTH,
Ludo’.