From: "Ludovic Courtès" <ludo@gnu.org>
To: Maxime Devos <maximedevos@telenet.be>
Cc: 54811@debbugs.gnu.org
Subject: [bug#54811] [PATCH 0/3] Support socket activation in 'guix publish' and 'guix-daemon'
Date: Tue, 12 Apr 2022 12:15:14 +0200 [thread overview]
Message-ID: <87a6cqehfx.fsf@gnu.org> (raw)
In-Reply-To: <4b82341ee0e4bdebbdf477ede00b6a8b33949788.camel@telenet.be> (Maxime Devos's message of "Tue, 12 Apr 2022 10:42:07 +0200")
Maxime Devos <maximedevos@telenet.be> skribis:
> Ludovic Courtès schreef op ma 11-04-2022 om 22:33 [+0200]:
>> > Alternatively, the shepherd could open the secret key file on
>> > behalf of
>> > ‘guix publish’ and send it together with the listening socket to
>> > ‘guix
>> > publish’.
>>
>> Sure, that’s feasible, but that’d require a custom protocol that I’d
>> rather avoid.
>
> I don't think it does, as long as we are using Shepherd and not SystemD
> (I don't think that SystemD supports opening regular files instead of
> sockets?), we could just
>
> * extend 'endpoint->listening-socket' (in Shepherd) to allow opening
> regular files (and not only actual sockets)
> * in 'systemd-socket' (in (guix scripts publish)), expect two startup
> file descriptors instead of one startup file descriptor, and return
> both (the first one is the actual listening socket, the second one
> the secret key file)
We could, but like I wrote, I’d rather stick to the existing systemd (or
inetd) protocol, especially since this extension wouldn’t buy us much IMO.
Ludo’.
next prev parent reply other threads:[~2022-04-12 10:17 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-09 9:12 [bug#54811] [PATCH 0/3] Support socket activation in 'guix publish' and 'guix-daemon' Ludovic Courtès
2022-04-09 9:13 ` [bug#54811] [PATCH 1/3] publish: Use SRFI-71 instead of SRFI-11 Ludovic Courtès
2022-04-09 9:13 ` [bug#54811] [PATCH 2/3] publish: Support systemd-style socket activation Ludovic Courtès
2022-04-09 9:20 ` Maxime Devos
2022-04-14 12:51 ` bug#54811: [PATCH 0/3] Support socket activation in 'guix publish' and 'guix-daemon' Ludovic Courtès
2022-04-09 9:13 ` [bug#54811] [PATCH 3/3] daemon: Support systemd-style socket activation Ludovic Courtès
2022-04-09 9:29 ` Maxime Devos
2022-04-09 20:28 ` [bug#54811] [PATCH 0/3] Support socket activation in 'guix publish' and 'guix-daemon' Ludovic Courtès
2022-04-09 9:19 ` Maxime Devos
2022-04-09 20:30 ` Ludovic Courtès
2022-04-09 20:49 ` Maxime Devos
2022-04-10 17:34 ` Ludovic Courtès
2022-04-10 17:43 ` Maxime Devos
2022-04-11 9:48 ` Ludovic Courtès
2022-04-11 10:06 ` Maxime Devos
2022-04-11 20:33 ` Ludovic Courtès
2022-04-12 8:42 ` Maxime Devos
2022-04-12 10:15 ` Ludovic Courtès [this message]
2022-04-12 8:48 ` Maxime Devos
2022-04-11 10:08 ` Maxime Devos
2022-04-11 20:34 ` Ludovic Courtès
2022-04-11 10:10 ` Maxime Devos
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=87a6cqehfx.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=54811@debbugs.gnu.org \
--cc=maximedevos@telenet.be \
/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).