From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.sysutils.supervision.general/625 Path: main.gmane.org!not-for-mail From: Alex Efros Newsgroups: gmane.comp.sysutils.supervision.general Subject: Re: runsvdir killed Date: Sun, 7 Nov 2004 21:40:12 +0200 Organization: asdfGroup Inc., http://www.asdfGroup.com/ Message-ID: <20041107194012.GF4568@home.power> References: <20041106184216.GB4568@home.power> <20041107135325.13303.qmail@fee8ec3a5e23da.315fe32.mid.smarden.org> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1099856431 3307 80.91.229.6 (7 Nov 2004 19:40:31 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sun, 7 Nov 2004 19:40:31 +0000 (UTC) Original-X-From: supervision-return-864-gcsg-supervision=m.gmane.org@list.skarnet.org Sun Nov 07 20:40:20 2004 Return-path: Original-Received: from antah.skarnet.org ([212.85.147.14] ident=qmailr) by deer.gmane.org with smtp (Exim 3.35 #1 (Debian)) id 1CQstf-0002tf-00 for ; Sun, 07 Nov 2004 20:40:19 +0100 Original-Received: (qmail 27692 invoked by uid 76); 7 Nov 2004 19:40:36 -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 27686 invoked from network); 7 Nov 2004 19:40:36 -0000 Original-To: supervision@list.skarnet.org Mail-Followup-To: supervision@list.skarnet.org Content-Disposition: inline In-Reply-To: <20041107135325.13303.qmail@fee8ec3a5e23da.315fe32.mid.smarden.org> User-Agent: Mutt/1.5.6i Xref: main.gmane.org gmane.comp.sysutils.supervision.general:625 X-Report-Spam: http://spam.gmane.org/gmane.comp.sysutils.supervision.general:625 Hi! On Sun, Nov 07, 2004 at 01:54:44PM +0000, Gerrit Pape wrote: > The runit program running as process 1 monitors the stage 2 which by > default is the runsvdir process. If runsvdir, and so /etc/runit/2, > crashes or exits 111, runit restarts /etc/runit/2. If it exits 0, runit > enters stage 3 and runs /etc/runit/3; see the runit(8) man page. Either > of them should happen on your system if /etc/runit/2 is terminated. I've configured "catch-all" log in /var/log/everything/ using pipe from runsvdir to svlogd in /etc/runit/2: #!/bin/sh PATH=...[cut]... exec env - PATH=$PATH runsvdir /var/service 'log: ...[cut]...' | svlogd /var/log/everything (this work because I've added "e*" in /var/log/*/config for most services which I want to see in everything-log plus I've added 2>&1 in most /service/*/log/run). So, if runsvdir is killed then /etc/runit/2 probably don't exit because svlogd is still running and runit-init don't restart /etc/runit/2. > You can send the runsvdir process a HUP signal to have stage 2 > restarted, but this should almost never be needed. I can't send HUP because it's killed. Probably right answer to my question is: kill svlogd executed in /etc/runit/2, so /etc/runit/2 will exit and runit-init will restart it. > This sounds really broken. I know. :( -- WBR, Alex.