From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.sysutils.supervision.general/1210 Path: news.gmane.org!not-for-mail From: Gerrit Pape Newsgroups: gmane.comp.sysutils.supervision.general Subject: Re: runit on Debian vserver (related to #306390) Date: Mon, 24 Jul 2006 10:02:40 +0000 Message-ID: <20060724100240.29400.qmail@7219b380d40f54.315fe32.mid.smarden.org> References: <20060719143952.BD73418EE4C@kolab.intevation.de> <200607201724.32202.bernhard@intevation.de> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1153735356 6526 80.91.229.2 (24 Jul 2006 10:02:36 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 24 Jul 2006 10:02:36 +0000 (UTC) Original-X-From: supervision-return-1446-gcsg-supervision=m.gmane.org@list.skarnet.org Mon Jul 24 12:02:33 2006 Return-path: Envelope-to: gcsg-supervision@gmane.org Original-Received: from antah.skarnet.org ([212.85.147.14]) by ciao.gmane.org with smtp (Exim 4.43) id 1G4xGW-00035r-RP for gcsg-supervision@gmane.org; Mon, 24 Jul 2006 12:02:21 +0200 Original-Received: (qmail 13701 invoked by uid 76); 24 Jul 2006 10:02:41 -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 13696 invoked from network); 24 Jul 2006 10:02:41 -0000 Original-To: supervision@list.skarnet.org Mail-Followup-To: supervision@list.skarnet.org Content-Disposition: inline In-Reply-To: <200607201724.32202.bernhard@intevation.de> Xref: news.gmane.org gmane.comp.sysutils.supervision.general:1210 Archived-At: On Thu, Jul 20, 2006 at 05:24:28PM +0200, Bernhard Reiter wrote: > yesterday I ran in the same problem as Debian bug #306390 > with runit-1.0.5-3. > I have just run into the same problem with runit 1.5.0-1 (Debian > stable).because the vserver was set up already I thought it was a runit bug. > My other administrator spend quite some time for it, > so the bug is not closed from my point of view. > > To close it, I suggest to add a hint when telinit q (aka kill -s HUP 1) fails: > > "You might be in a vserver environment where telinit q does not work. > A workaround is to comment out kill -s HUB 1 in the postinst script > and start runit differently. > Another workaround one is to make the vserver recognise > telinit and use inittab to start things (initstyle plain)." > > Of course, in case of failure the postinst should remove > the inittab entry again, to avoid problems in the next run. Ok, thanks for the hint, I'll see what I can do. > On my installation the problem is solved, > but it took a bit of time to find the problem and I would save others > the time with this hint. > > Thanks a lot for runit, I find it a nice software with well written > documentation and Free Software. Thanks, Gerrit.