MIME-Version: 1.0
Date: Thu, 27 Aug 2020 13:20:29 +0000
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: "Francesco Colista" <fcolista@alpinelinux.org>
Message-ID: <ff2f9139bf743abd7303b89f10fc9549@alpinelinux.org>
Subject: Re: Use of supervise-daemon in Alpine
To: "Leonardo" <rnalrd@gmail.com>, "Natanael Copa" <ncopa@alpinelinux.org>
Cc: ~alpine/devel@lists.alpinelinux.org,
 "=?utf-8?B?U8O2cmVuIFRlbXBlbA==?=" <soeren@soeren-tempel.net>
In-Reply-To: <dea709f7-94b7-f02c-929a-f7368f05bf6d@gmail.com>
References: <dea709f7-94b7-f02c-929a-f7368f05bf6d@gmail.com>
 <3LLUI2KOULSYM.359WA6HATX45B@8pit.net>
 <20200821191507.7857010b@ncopa-macbook.copa.dup.pw>

27 agosto 2020 14:49, "Leonardo" <rnalrd@gmail.com> wrote:=0A=0A =0A> So =
what should be the approach? I see:=0A> =0A> 1. let the developer choose =
between supervised/unsupervised daemon=0A> =0A> 2. provide two init scrip=
ts, supervised and unsupervised=0A> =0A> 3. provide an "hybrid" init scri=
pt which has a configurable user option=0A> to choose between supervised/=
unsupervised daemon=0A> =0A> 4. other?=0A> =0A> I'm asking these question=
s because I got for the first time a MR which=0A> adopts solution 2, whic=
h I never saw so far. It seems to me that=0A> solution 1 was adopted so f=
ar.=0A> =0A> Or if there's no single solution, which should be avoided?=
=0A=0AI would for the second option, because:=0A=0A1. I'm the author of t=
he MR :)=0A2. Is the most flexible solution:=0A=0AOption n.1 is a limitat=
ion, option n.3 is difficult to maintain if/when we are going to implemen=
t other supervisor, like s6.=0AThe second option allow also the two init =
to co-exists, which in some corner cases this might be wanted.=0A=0A=0A.:=
 Francesco Colista=0A.: Alpine Linux Core Dev Team