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: "Amaresh Kotekal" <amareshkotekal@gmail.com>,
	"supervision@list.skarnet.org" <supervision@list.skarnet.org>
Subject: Re: Dependencies in S6
Date: Wed, 21 Oct 2020 13:26:25 +0000
Message-ID: <em81fd4f46-86a3-4d4d-86db-94865393f2f7@elzian> (raw)
In-Reply-To: <CADYBkpEsEC7W-kv+pS4RizYXu1mkC2TdHYYN=DH6=ZDMhWnjTA@mail.gmail.com>


  Hi Amaresh,

  As long as service B depends on service A, A and B will never start
in parallel; B will always start when A is ready.

  "A is ready" means:
   - if A is a oneshot: when the script has completed
   - if A is a longrun:
     * if there is a notification-fd file in the service definition
directory: when the daemon has notified readiness
     * if there is no such file: as soon as the run script has started
(which is not a good readiness indicator; it is akin to starting B
_right after A_, essentially in parallel, so you may have race
conditions here - which is why you should always use readiness
notifications.)


>Secnario 1:
>1. A & B are one shot services in a s6-rc bundle. Service B is dependent on
>A. ( added in dependency file).
>2. I think Service B will start after the completion of service A ( A then
>B, in serial manner ) is it correct ? or
>3. Service B will start immediately after the service A as started (in a
>parallel manner) ?

  Serial manner, A then B.


>Secnario 2:
>1. A is one shot service and B is a long run service. Service B is
>dependent on Service A.
>2. Service B will start, once th service A as completed (in serial manner)
>? or
>3. Service B will start immediately after the service A as started (in a
>parallel manner) ?

  Serial manner, A then B.


>Secnario 3:
>1. A is a long run service and B is a one shot service. Service B is
>dependent on Service A.
>2. Service B will start immediately after the service A as started (in a
>parallel manner) ?
>3. Do I need to use notification mechanism if I want to start service B
>after A service as reached particular point in execution

  Yes, you need notification; if you don't, then B will start
immediately after A.


>Secnario 4:
>1. A & B both are long run services. Service B is dependent on Service A.
>2. Service B will start immediately after the service A as started (in a
>parallel manner) ?

  Same as above: almost-parallel manner if A does not use notification,
serial manner if it does.


>  If one shot service are dependent on other one shot services. They will be
>started in serial manner one after the other ?

  That is your Scenario 1 above.

  If the case is: "C depends on A and B, but A and B are independent",
then:
  * A and B are started in parallel
  * when both A and B are ready, then C is started.

  Hope this helps,

--
  Laurent


  parent reply	other threads:[~2020-10-21 13:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-21 10:10 Amaresh Kotekal
2020-10-21 13:17 ` Guillermo
2020-10-21 13:23 ` Crest
2020-10-21 13:26 ` Laurent Bercot [this message]
2020-10-21 19:14   ` Steve Litt

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=em81fd4f46-86a3-4d4d-86db-94865393f2f7@elzian \
    --to=ska-supervision@skarnet.org \
    --cc=amareshkotekal@gmail.com \
    --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

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