From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.3 required=5.0 tests=MAILING_LIST_MULTI, NICE_REPLY_A autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 23529 invoked from network); 4 Nov 2020 10:11:10 -0000 Received: from alyss.skarnet.org (95.142.172.232) by inbox.vuxu.org with ESMTPUTF8; 4 Nov 2020 10:11:10 -0000 Received: (qmail 21041 invoked by uid 89); 4 Nov 2020 10:11:34 -0000 Mailing-List: contact supervision-help@list.skarnet.org; run by ezmlm Sender: Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Received: (qmail 21034 invoked from network); 4 Nov 2020 10:11:34 -0000 Subject: Re: S6-log To: supervision@list.skarnet.org References: From: Crest Message-ID: <5dd3997a-310e-5f50-9d94-5ccf793eb259@rlwinm.de> Date: Wed, 4 Nov 2020 11:11:00 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:68.0) Gecko/20100101 Thunderbird/68.12.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US 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 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.