supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: supervision@list.skarnet.org
Subject: socket-activate is published [was: Re: listen(1)]
Date: Fri, 15 Feb 2019 11:04:41 -0500	[thread overview]
Message-ID: <87imxlt4va.fsf@fifthhorseman.net> (raw)
In-Reply-To: <87twesty2o.fsf@alice.fifthhorseman.net>

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

Hi folks--

On Wed 2016-08-10 11:58:55 -0400, Daniel Kahn Gillmor wrote:
> The tool is a binary called "listen", which tries to open a series of
> sockets and then exec()'s another command with those file descriptors
> already open.  It adopts a convention for identifying those file
> descriptors from systemd's socket activation features, so that it can be
> used to supervise any daemon that follows the same convention.

Just wanted to let folks on this list know that if you are interested in
this, i've renamed "listen" to "socket-activate", and finally gotten
around to publishing an implementation for broader general consumption.

It's at https://gitlab.com/dkg/socket-activate, and it's a very simple
python3 implementation of the supervisor's side of the sd_listen_fds(3)
convention.  It depends only on python3's stdlib, so while it's not as
minimal as a C implementation would be, it's still pretty lean.

In discussions over on https://bugs.debian.org/922353, Guillem Jover
suggested that start-stop-daemon might also be willing to accept
comparable functionality to support the same convention, to enable
support for daemons that use it.

Happy hacking,

    --dkg

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

           reply	other threads:[~2019-02-15 16:04 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <87twesty2o.fsf@alice.fifthhorseman.net>]

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

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

  git send-email \
    --in-reply-to=87imxlt4va.fsf@fifthhorseman.net \
    --to=dkg@fifthhorseman.net \
    --cc=supervision@list.skarnet.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.
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 NNTP newsgroup(s).