supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: "Laurent Bercot" <ska-supervision@skarnet.org>
To: "Xavier Stonestreet" <xstonestreet@gmail.com>,
	supervision@list.skarnet.org
Subject: Re: s6-rc: timeout questions
Date: Tue, 17 Nov 2020 21:53:28 +0000
Message-ID: <emb4766da9-1c6f-41c1-b36c-722e61032fb6@elzian> (raw)
In-Reply-To: <CAK-rGMLLRk1wZzDRPZs2JOzirizAKR6w3orOG4=qKOh6n13xBg@mail.gmail.com>

>- Am I correct in thinking that if a service has properly configured
>timeout-kill and timeout-finish, timeout-down becomes unnecessary and
>even undesirable as it can leave services in an undefined state limbo?
>I know the documentation pretty much says so, but I'm still a bit
>confused by the existence of timeout-down to begin with, if it's
>redundant and unhelpful.

  timeout-kill and timeout-finish are a s6 thing: if present, they're
just copied as is to the service directory that will be managed by
the s6 supervision tree.
  timeout-up and timeout-down are specific to s6-rc: they will be
embedded into the compile database. They do not interact with s6 at
all, they're just a rule for the s6-rc state machine: if the
service does not report being up (resp. down) by the timeout, then
s6-rc marks the transition as failed and stops looking at what
happens with the service.

  For longruns, yes, timeout-kill ensures that the service will
eventually be brought down no matter what. But there are cases where
you *do not want* to kill -9 a daemon (and need a timeout-kill of 0).
timeout-down is useful here, even if it's a pretty niche case.

  And then, of course, the point is that it's needed for oneshots,
which do not have the s6 mechanisms.


>- Can you confirm that timeout-up and timeout-down are also used with
>oneshots? They are defined in the s6-rc-compile documentation, but the
>s6-rc documentation doesn't specifically mention them for oneshots
>state transitions.

  Yes, I confirm that they're also (and primarily) used with oneshots.
They're defined in the "atomic services" section, which comprises
longruns *and* oneshots.

--
  Laurent


  reply	other threads:[~2020-11-17 21:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-17 15:53 Xavier Stonestreet
2020-11-17 21:53 ` Laurent Bercot [this message]
2020-11-18 17:49   ` Xavier Stonestreet
2020-11-18 19:06     ` Laurent Bercot
2020-11-20 10:30       ` Xavier Stonestreet

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=emb4766da9-1c6f-41c1-b36c-722e61032fb6@elzian \
    --to=ska-supervision@skarnet.org \
    --cc=supervision@list.skarnet.org \
    --cc=xstonestreet@gmail.com \
    /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

supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://inbox.vuxu.org/supervision

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V1 supervision supervision/ http://inbox.vuxu.org/supervision \
		subscribe@list.skarnet.org
	public-inbox-index supervision

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.vuxu.org/vuxu.archive.supervision.general


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git