GNU bug report logs -
#54811
[PATCH 0/3] Support socket activation in 'guix publish' and 'guix-daemon'
Previous Next
Reported by: Ludovic Courtès <ludo <at> gnu.org>
Date: Sat, 9 Apr 2022 09:13:01 UTC
Severity: normal
Tags: patch
Done: Ludovic Courtès <ludo <at> gnu.org>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
[Message part 1 (text/plain, inline)]
Your message dated Thu, 14 Apr 2022 14:51:58 +0200
with message-id <87zgkn96a9.fsf_-_ <at> gnu.org>
and subject line Re: bug#54811: [PATCH 0/3] Support socket activation in 'guix publish' and 'guix-daemon'
has caused the debbugs.gnu.org bug report #54811,
regarding [PATCH 0/3] Support socket activation in 'guix publish' and 'guix-daemon'
to be marked as done.
(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)
--
54811: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=54811
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
Hello!
Now that we have this fancy new Shepherd, we can have our daemons
started lazily via “socket activation” like all the cool kids have
been doing. :-)
Next steps: update the ‘guix’ package, update the .service files,
and update (gnu services base) (I’m not entirely sure we can start
‘guix-daemon’ via socket activation though due to the container
shenanigans in there.)
Thoughts?
Ludo’.
Ludovic Courtès (3):
publish: Use SRFI-71 instead of SRFI-11.
publish: Support systemd-style socket activation.
daemon: Support systemd-style socket activation.
doc/guix.texi | 11 ++++++++-
guix/scripts/publish.scm | 39 +++++++++++++++++++++++++-------
nix/nix-daemon/guix-daemon.cc | 42 ++++++++++++++++++++++++++++++-----
3 files changed, 78 insertions(+), 14 deletions(-)
base-commit: 0996d48d0e79a360e0d5583b812cd565f62ca32e
--
2.35.1
[Message part 3 (message/rfc822, inline)]
Hi,
Maxime Devos <maximedevos <at> telenet.be> skribis:
> Ludovic Courtès schreef op za 09-04-2022 om 11:13 [+0200]:
>> + "If this program is being spawned through systemd-style \"socket
>> +activation\", whereby the listening socket is passed as file descriptor 3,
>> +return the corresponding socket."
>
> And if it isn't, what is returned then?
>
> "Otherwise, return #false."
I fixed that and pushed:
5f74169e8e daemon: Support systemd-style socket activation.
b9233cb9a8 publish: Support systemd-style socket activation.
17c6d00b57 publish: Use SRFI-71 instead of SRFI-11.
Thanks,
Ludo’.
This bug report was last modified 3 years and 38 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.