RE: The udev question & understanding what runsvdir "means"

From: James Powell <james4591_at_hotmail.com>
Date: Thu, 2 Oct 2014 18:16:28 -0400

You could always implement in Stage 2 before the Runit/s6 service execution a call to a legacy rc.local to load classic init scripts. We did it with runit-for-lfs and it works well.

Sent from my Windows Phone
________________________________
From: Avery Payne<mailto:avery.p.payne_at_gmail.com>
Sent: ‎10/‎2/‎2014 5:43 PM
To: supervision_at_list.skarnet.org<mailto:supervision_at_list.skarnet.org>
Subject: Re: The udev question & understanding what runsvdir "means"

On Wed, Oct 1, 2014 at 9:33 AM, Colin Booth <cathexis_at_gmail.com> wrote:

>
> If you're running this on a debian system, judicious use of
> `update-rc.d $service disable' will help with dpkg trying to run
> things over and over again (such as the dbus case). At least, I've
> disabled it across all run levels, shoved it into supervision, and
> haven't had any issues.
>
Part of the project will be to provide some back-compat for SysV init. So,
eventually, when apt-get upgrade rolls around, calls to the original init.d
scripts will actually trigger 'sv restart $(service)', and services will
restart under runit instead of under SysV. But for now, yeah, I'll just
shut them all down.
Received on Thu Oct 02 2014 - 22:16:28 UTC