supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: João <>
To: Alexis <>
Subject: Re: gpg-agent runit run script
Date: Fri, 30 Sep 2022 11:06:29 +0200	[thread overview]
Message-ID: <YzaxXwBDBPcd7Dt0@pagode> (raw)
In-Reply-To: <87pmfegykh.fsf@ada>

Hello Alexis,

On Thu, Sep 29, 2022 at 10:12:49PM +1000, Alexis wrote:
> João <> writes:
> > The Void linux manual shows gpg-agent running as an example, but they
> > don't show
> > the run script, so I don't know how they set it up.
> >
> Duncaen's run script for gpg-agent is here:
> It's actually an execline script that makes use of
> s6-ipcserver-socketbinder. Also note that the script calls gpg-agent with
> `--supervise`.

Thank you for this. It is helpful to look at an example.

> > This is a pity as gpg-agent is a long running process which is the
> > sort of thing
> > you would want to run under supervision.
> Well, the typical reason we want to run something under supervision is to
> ensure it's up, because (a) there are processes relying on it being up, and
> (b) those processes aren't themselves able to start the relevant process.
> But this isn't the case with gpg-agent: the main programs that utilise it
> know how to start it themselves if necessary, so it doesn't matter if a
> gpg-agent process exits abnormally, as a new one will get created when
> required.

You have a point. But I guess you still loose a common consistent way of
checking the status and controlling the processes in your system.

Best regards,

      parent reply	other threads:[~2022-09-30  9:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-20 21:51 João
2022-09-26 17:04 ` Alyssa Ross
2022-09-29  9:20   ` João
2022-09-29  9:23     ` Ellenor Bjornsdottir
2022-09-28 18:46 ` Guillermo
2022-09-29  9:37   ` João Pedro Malhado
2022-09-29 12:12     ` Alexis
2022-09-29 21:56       ` Guillermo
2022-09-30  2:00         ` Alexis
2022-09-30  9:06       ` João [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:

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

  git send-email \
    --in-reply-to=YzaxXwBDBPcd7Dt0@pagode \ \ \ \

* 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).