unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Tomas Volf <~@wolfsden.cz>
Cc: 74534-done@debbugs.gnu.org, Jelle Licht <jlicht@fsfe.org>
Subject: bug#74534: [shepherd] guix-home managed shepherd shares process group with shell
Date: Thu, 28 Nov 2024 08:48:34 +0100	[thread overview]
Message-ID: <87ed2v94tp.fsf@gnu.org> (raw)
In-Reply-To: <87v7wbcb59.fsf@wolfsden.cz> (Tomas Volf's message of "Mon, 25 Nov 2024 21:26:58 +0100")

Hello!

Tomas Volf <~@wolfsden.cz> skribis:

> Jelle Licht <jlicht@fsfe.org> writes:
>
>> Addendum:
>> running `herd eval root "(setsid)"` solves my particular issue, making
>> ^C on my shell no longer kill my user shepherd.

Fixed in Shepherd commit 2b41e5bad65e783c7a9cc4d7a3f460cab6b64285.

> Oh, that is neat.  I did not realize this can be fixed like that without
> modifying shepherd's source code.  I turned it into a service that I
> added into my home-environment:
>
>      ;; Bug 74534: Home shepherd can be killed by ^C
>      (simple-service 'call-setsid-in-home-shepherd home-shepherd-service-type
>                      (list
>                       (shepherd-service
>                        (documentation "Give shepherd its own process group.")
>                        (provision '(setsid))
>                        (start #~(lambda _ (setsid) #t))
>                        (one-shot? #t))))

Nice workaound.

Thank you, comrades!

Ludo’.




      reply	other threads:[~2024-11-28  7:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-25 18:42 bug#74534: [shepherd] guix-home managed shepherd shares process group with shell Jelle Licht
2024-11-25 18:52 ` Jelle Licht
2024-11-25 20:26   ` Tomas Volf
2024-11-28  7:48     ` Ludovic Courtès [this message]

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=87ed2v94tp.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=74534-done@debbugs.gnu.org \
    --cc=jlicht@fsfe.org \
    --cc=~@wolfsden.cz \
    /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).