From: Crest <email@example.com> To: firstname.lastname@example.org Subject: Re: Dependencies in S6 Date: Wed, 21 Oct 2020 15:23:21 +0200 Message-ID: <email@example.com> (raw) In-Reply-To: <CADYBkpEsEC7W-kv+pS4RizYXu1mkC2TdHYYN=DH6=ZDMhWnjTA@mail.gmail.com> On 21.10.20 12:10, Amaresh Kotekal wrote: > Hi Team, > > I have some doubt on dependencies file in S6. > > 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) ? > > 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) ? > > 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 > > 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) ? > > If one shot service are dependent on other one shot services. They will be > started in serial manner one after the other ? The s6-rc service manager is always concurrent while respecting dependencies. It starts all services as soon as their requirements are satisfied. Having a single service depend on a single other service is just a special case of the more general dependency resolution s6-rc does.
next prev parent reply other threads:[~2020-10-21 13:23 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 [this message] 2020-10-21 13:26 ` Laurent Bercot 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 \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.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 \ email@example.com 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