unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: "Ludovic Courtès" <ludo@gnu.org>, "John Soo" <jsoo1@asu.edu>,
	guix-devel@gnu.org
Subject: Re: RFC: subcommand to pause/resume builds
Date: Tue, 03 Nov 2020 18:19:36 +0100	[thread overview]
Message-ID: <87blge4atz.fsf@nckx> (raw)
In-Reply-To: <87ft5q4d0i.fsf@nckx>

[-- Attachment #1: Type: text/plain, Size: 831 bytes --]

After playing around with the daemon I agree that it plays a 
little too loose with processes to make this upstream material ATM 
(groups? shepherd? *shrug*).

To close:

Tobias Geerinckx-Rice 写道:
> However, this is FUD:
>
>> Last, you’d need to send SIGTSTP to the whole process group of 
>> the
>> build, like so (I think, haven’t tried):

Re-reading this I wonder if you misread SIGSTOP as SIGTSTP?  The 
two are not related.  SIGSTOP cannot be handled or blocked.

It's possible to *detect*, like one can detect almost anything 
because, but you'd be going out of your way to do so.  I still 
think the concern is oddly specific & theoretical.

Build processes *could* be using rowhammer to deliberately crash 
if you're browsing Reddit, too, and who could blame them.

Kind regards,

T G-R

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]

  parent reply	other threads:[~2020-11-03 17:19 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
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 [this message]
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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87blge4atz.fsf@nckx \
    --to=me@tobias.gr \
    --cc=guix-devel@gnu.org \
    --cc=jsoo1@asu.edu \
    --cc=ludo@gnu.org \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).