From: Guillermo <email@example.com> To: Supervision <firstname.lastname@example.org> Subject: Re: S6 bundle Date: Tue, 20 Oct 2020 19:51:03 -0300 Message-ID: <CADQ2Nw-HUp0QMygpTndmMu-Q-TFHamCXsC9BBid+QhmgqUd_zQ@mail.gmail.com> (raw) In-Reply-To: <CADYBkpH65+uQBpoDhm_xmZe+7rD3wCcFyfvfhsyc8GxqeFQnBQ@mail.gmail.com> Hi, Strictly speaking, you should say "s6-rc bundle", not "s6 bundle". El mar., 20 oct. 2020 a las 13:00, Amaresh Kotekal escribió: > > Contents of S6 bundle will run serially one after the other or they will > run parallely ? Specifying the name of a bundle in an 's6-rc -u change' command with make s6-rc start all services named in its 'contents' file. How they will start is governed by dependencies (i.e. the contents of those services' 'dependencies' file), as usual. If no service in the bundle depends on any of the others, they start in parallel. If some of them depend on others, you'll have subsets of services that start serially. > If any one service fails in bundle is other services will continue to run > or they will be not started ? Again, this is governed by dependencies. If no service in the bundle depends on any of the others, whether one service fails or not does not impact the rest of them. If some service in the bundle depends on others, and any of those fails, it will not be started, as usual. G.
next prev parent reply other threads:[~2020-10-20 22:51 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-10-20 16:00 Amaresh Kotekal 2020-10-20 22:51 ` Guillermo [this message] 2020-10-21 5:37 ` Ready to pass or crash eric vidal 2020-10-21 5:40 ` eric vidal
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=CADQ2Nw-HUp0QMygpTndmMu-Q-TFHamCXsC9BBid+QhmgqUd_zQ@mail.gmail.com \ --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