Re: Using runit-init on debian/Jessie in place of sysvinit/systemd

From: Avery Payne <avery.p.payne_at_gmail.com>
Date: Fri, 2 Jan 2015 02:58:01 -0800

Ugh, I hate replying to the list with Gmail. Sorry for the confusion and
the embedded header, I'm forwarding it so it can be seen by others.

On Fri, Jan 2, 2015 at 2:54 AM, Avery Payne <avery.p.payne_at_gmail.com> wrote:

>
> On Thu, Jan 1, 2015 at 4:31 PM, toki clover <tokiclover_at_gmail.com> wrote:
>
>> ---------- Forwarded message ----------
>> From: toki clover <tokiclover_at_gmail.com>
>> Date: 2015-01-02 1:30 GMT+01:00
>> Subject: Re: Using runit-init on debian/Jessie in place of
>> sysvinit/systemd
>> To: Luke Diamand <luke_at_diamand.org>
>>
>>
>> First, it's a bit crazy to use runit for init+service management entirely
>> because:
>>
>
> Oh, I'm crazy? Perhaps I should put on Mad Scientist goggles and a lab
> coat? :-)
>
>
>>
>> - It's completely crazy to supervise every service because; first, every
>> service
>> won't fit in if it's not a daemon;
>
>
> I'm working on this issue. This may be achievable with just shell script
> alone; but I'm looking at something very different from other solutions.
>
>
>> second supervising every daemon is
>> dangerous.
>>
>
> How? In what context? I'm curious.
>
>
>> - Second, runit (or s6 for that matter) lack any decent service
>> dependency,
>> actually both completely ignore the problem (athough s6 may change this in
>> in a near futur.)
>>
>
> I have been working on a shell-script prototype that would bring up
> services before launching a daemon. It is not complete and I am still
> working out the details. If it works, then I will include it as a
> "standard feature" of supervision-scripts.
>
>
>> - Third, do not forget the overhead of supervision (an extra instance per
>> daemon.)
>>
>
> There was some discussion on the mailing list about this very topic.
>
>
>> Stuffing stage 1 is suicidal...
>>
>
> It's only suicidal if you don't have another init system around. I kept
> chunks of SysV intact on my home system for that reason, but it defaults to
> and starts with runit currently. Since the switch over, I've not needed
> SysV beyond looking at what Debian currently does inside of init.d scripts.
>
>
Received on Fri Jan 02 2015 - 10:58:01 UTC

This archive was generated by hypermail 2.3.0 : Sun May 09 2021 - 19:44:18 UTC