From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.sysutils.supervision.general/1601 Path: news.gmane.org!not-for-mail From: Bernhard Graf Newsgroups: gmane.comp.sysutils.supervision.general Subject: Re: using runit as init Date: Tue, 8 Jan 2008 23:28:06 +0100 Message-ID: <200801082328.06568.list-supervision@augensalat.de> References: <200801032151.21524.list-supervision@augensalat.de> <200801060017.52406.list-supervision@augensalat.de> <20080108071144.GJ41886@linsec.ca> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1199831302 4346 80.91.229.12 (8 Jan 2008 22:28:22 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 8 Jan 2008 22:28:22 +0000 (UTC) To: supervision@list.skarnet.org Original-X-From: supervision-return-1836-gcsg-supervision=m.gmane.org@list.skarnet.org Tue Jan 08 23:28:42 2008 Return-path: Envelope-to: gcsg-supervision@gmane.org Original-Received: from antah.skarnet.org ([212.85.147.14]) by lo.gmane.org with smtp (Exim 4.50) id 1JCMvy-0003di-UK for gcsg-supervision@gmane.org; Tue, 08 Jan 2008 23:28:35 +0100 Original-Received: (qmail 18822 invoked by uid 76); 8 Jan 2008 22:28:17 -0000 Mailing-List: contact supervision-help@list.skarnet.org; run by ezmlm List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Archive: Original-Received: (qmail 18816 invoked from network); 8 Jan 2008 22:28:17 -0000 User-Agent: KMail/1.9.1 In-Reply-To: <20080108071144.GJ41886@linsec.ca> Content-Disposition: inline Xref: news.gmane.org gmane.comp.sysutils.supervision.general:1601 Archived-At: Vincent Danen wrote: > You may also be interested in what Annvix has done. Annvix has used > runit for init for quite a few years now, and very successfully. It > still handles traditional "initscripts", but doesn't handle > number-based runlevels or runlevel switching (largely due to the fact > that Annvix has no GUI and thus has no real need for that). Of course I also discovered Annvix already. Nice work (and a lot of, I suppose). Brought me to execline among other things, which I knew for quite some time, but never actually used so far. > That's got the relevant runit scripts we use to handle init. Note > that we don't completely do away with sysvinit... there are some > useful tools that come with it; we just don't use sysvinit's init. Actually I'm missing two essential things in runit, that would allow to replace "standard" (Linux/SysV) init while keeping the start/Stop scripts in the beginning: - possibility to set no-respawn mode for a service, instead run command (e.g. "/etc/init.d/service start") when service appears in runsvdir's directory and run other command (e.g. "/etc/init.d/service stop) when it disappears - service dependencies Another interesting project is ninit [1] and its ancestor minit [2] [1] http://riemann.fmi.uni-sofia.bg/ninit/ [2] http://www.fefe.de/minit/ Those have dependencies and can start services w/o respawn, but they don't have a svscan-like function, they can start dependend services at start-up - later services must be brought up and down by [mn]svc command. Potentially this would fit better into an existing SysV-based init scheme, because "/etc/init.d/service start" would just execute [mn]svc -u service and "/etc/init.d/service stop" [mn]svc -d service. Still runit is much more elegant IMHO by starting and removing services as they appear and disappear - this would make runlevels really easy. -- Bernhard Graf