Received: from cogitri.dev (cogitri.dev [207.180.226.74]) by nld3-dev1.alpinelinux.org (Postfix) with ESMTPS id 115E27819A4 for <~alpine/devel@lists.alpinelinux.org>; Thu, 27 Aug 2020 13:27:33 +0000 (UTC) X-Virus-Scanned: Yes Message-ID: <799e151a9764838b5b0e273da3626e471976edb7.camel@cogitri.dev> DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cogitri.dev; s=mail; t=1598534843; bh=kMUrazOr3sLJGiKdk2q++3jpfn+kjbuxHhlgjBSs/zY=; h=Subject:From:To:Cc:In-Reply-To:References; b=w9I8CCw5nzUWOH3q+Zbaklu0ffq5KRvWpiOlisjtffkry1jYKJ6z/QD/OHso77jAx KZYKgfXPMOIf0Kxjdlp98BoVwt3PVygS60kgrpALFAXxtAgkhEeY1euIcCMF0y439y NklCKPV6aXHegbBsYT9qPNT4QK96eyut5TjNjMrYKzhre3CT2zLysMhHrydtYifj3C oFtapUfsur1ldakc0aT5+/mmA+B5HARneRdC3yCrXhqkmAC262YlzZPJsWt5QB6f0m WH5jSstZn0UjYwX5C0jeoucQ8+c86E3GKwtIcRfGrC0DWWh05N8RLITjkAngqfqpA7 xgOmAmU628YdA== Subject: Re: Use of supervise-daemon in Alpine From: Rasmus Thomsen To: Francesco Colista , Leonardo , Natanael Copa Cc: ~alpine/devel@lists.alpinelinux.org, =?ISO-8859-1?Q?S=F6ren?= Tempel Date: Thu, 27 Aug 2020 15:27:22 +0200 In-Reply-To: References: <3LLUI2KOULSYM.359WA6HATX45B@8pit.net> <20200821191507.7857010b@ncopa-macbook.copa.dup.pw> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit On Thu, 2020-08-27 at 13:20 +0000, Francesco Colista wrote: > 27 agosto 2020 14:49, "Leonardo" wrote: > > > > So what should be the approach? I see: > > > > 1. let the developer choose between supervised/unsupervised daemon > > > > 2. provide two init scripts, supervised and unsupervised > > > > 3. provide an "hybrid" init script which has a configurable user > > option > > to choose between supervised/unsupervised daemon > > > > 4. other? > > > > I'm asking these questions because I got for the first time a MR > > which > > adopts solution 2, which I never saw so far. It seems to me that > > solution 1 was adopted so far. > > > > Or if there's no single solution, which should be avoided? > > I would for the second option, because: > > 1. I'm the author of the MR :) > 2. Is the most flexible solution: > > Option n.1 is a limitation, option n.3 is difficult to maintain > if/when we are going to implement other supervisor, like s6. > The second option allow also the two init to co-exists, which in some > corner cases this might be wanted. I think in the majority of cases we don't need an unsupervised init script (what's the rationale for having it in that MR (and what MR are we talking about? :D)), since supervision has many advantges, as mentioned in the thread already. IMHO it'd be best to just switch as much as possible over to supervise-daemon before 3.13. I'd rather not maintain two different sets of init scripts if possible. Regards, Rasmus Thomsen > > .: Francesco Colista > .: Alpine Linux Core Dev Team