unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 54811@debbugs.gnu.org
Subject: [bug#54811] [PATCH 0/3] Support socket activation in 'guix publish' and 'guix-daemon'
Date: Mon, 11 Apr 2022 12:10:23 +0200	[thread overview]
Message-ID: <49b1b912660173c856a9552a073f29d93d7a6a35.camel@telenet.be> (raw)
In-Reply-To: <877d7wkl18.fsf@gnu.org>

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

Ludovic Courtès schreef op ma 11-04-2022 om 11:48 [+0200]:
> > > One thing is sure: when ‘--advertise’ is used, we shouldn’t use
> > > socket
> > > activation or nothing will be advertised.  Is that what you mean?
> > 
> > No, how would socket activation prevent advertising?
> 
> As currently implemented in the Shepherd, socket activation means
> that
> the process is started lazily, the first time a connection request is
> made.  If the ‘guix publish’ process isn’t started, then DNS-SD
> publication doesn’t happen.

Right, the DNS-SD publication would only happen when ‘guix publish’ is
contacted directly, e.g. somebody doing "guix build --substitute-
urls=http://...".

Greetings,
Maxime.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

      parent reply	other threads:[~2022-04-11 10:14 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
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 [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=49b1b912660173c856a9552a073f29d93d7a6a35.camel@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=54811@debbugs.gnu.org \
    --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).