From: Crest <crest@rlwinm.de>
To: supervision@list.skarnet.org
Subject: Re: S6-log
Date: Wed, 4 Nov 2020 11:11:00 +0100 [thread overview]
Message-ID: <5dd3997a-310e-5f50-9d94-5ccf793eb259@rlwinm.de> (raw)
In-Reply-To: <CAH9hU4Lsvocn=Wv+O-_tQLDMCNAnCDnYo=bAZRiqFXamOdG-aA@mail.gmail.com>
On 04.11.20 10:42, billa chaitanya wrote:
> Hi team,
>
> 1) does the log service of a corresponding long run service goes down when
> the long run service is made down using some s6 commands? (like s6-rc -d
> change <long run service name>
It does not go down, because the dependency is the other way around. The
service requires its log service, but the log service doesn't require
its service to start (it's just useless without it).
s6-rc -u change foo starts a service and all its dependencies (including
its log service). s6-rc -d change bar stops all services depending on a
service and the service. Stopping the log service stops the service as
well. Starting the service starts the log service.
> 2) Shall we use s6-log for one shot services too?
Oneshot services are started by the s6 oneshot runner. This long running
service is required to start oneshots in a clean environment.
> 3) is there any command-line option we can provide to s6-log for stopping
> the running s6-log?
What problem are you trying to solve? s6-log shouldn't have deal with
replacing an other s6-log process itself.
next prev parent reply other threads:[~2020-11-04 10:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-04 9:42 S6-log billa chaitanya
2020-11-04 10:11 ` Crest [this message]
2020-11-04 17:35 ` S6-log Laurent Bercot
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=5dd3997a-310e-5f50-9d94-5ccf793eb259@rlwinm.de \
--to=crest@rlwinm.de \
--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
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).