From: "Ludovic Courtès" <ludo@gnu.org>
To: John Soo <jsoo1@asu.edu>
Cc: guix-devel@gnu.org
Subject: Re: RFC: subcommand to pause/resume builds
Date: Tue, 03 Nov 2020 14:53:07 +0100 [thread overview]
Message-ID: <87zh3yczss.fsf@gnu.org> (raw)
In-Reply-To: <87r1pbzixl.fsf@asu.edu> (John Soo's message of "Mon, 02 Nov 2020 10:56:38 -0800")
Hi,
John Soo <jsoo1@asu.edu> skribis:
> I was looking to pause a long build today and asked on IRC how to
> accomplish pause/resume. It seems this is possible already with the
> following:
>
> kill --signal SIGSTOP|SIGCONT {pids-of-build-process-tree}
>
> There is already a command to list the processes associated to guix
> commands: guix processes. Perhaps pause/resume can be a subcommand or
> set of flags to guix processes. The following is the first thing that
> comes to mind:
>
> guix processes --pause package-name ... --resume package-name ...
>
> What do you think?
First, note that the daemon is unaware of “packages”, it only knows
about “derivations”.
Second, ‘guix processes’ is nice but it uses low-level heuristics to
determine what daemon sessions are open, what their clients are, and
what they’re building; it resorts to heuristics because the daemon as it
stands doesn’t have a way to communicate its current state. It works
well in practice, but still I wouldn’t go too far building around it.
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.
Conclusion: I don’t think we can implement this reliably.
HTH!
Ludo’.
next prev parent reply other threads:[~2020-11-03 13:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-02 18:56 RFC: subcommand to pause/resume builds John Soo
2020-11-03 13:53 ` Ludovic Courtès [this message]
2020-11-03 14:41 ` John Soo
2020-11-03 16:32 ` Tobias Geerinckx-Rice
2020-11-03 17:12 ` John Soo
2020-11-06 8:56 ` Ludovic Courtès
2020-11-03 17:19 ` Tobias Geerinckx-Rice
2020-11-03 18:27 ` John Soo
2020-11-03 20:01 ` John Soo
2020-11-06 8:58 ` Ludovic Courtès
2020-11-06 23:00 ` John Soo
2020-11-04 10:28 ` Bengt Richter
2020-11-06 21:11 ` Mark H Weaver
2020-11-08 16:30 ` Ludovic Courtès
-- strict thread matches above, loose matches on Subject: below --
2020-11-05 4:37 John Soo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zh3yczss.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=jsoo1@asu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.