Re: runsvdir killed

[Alex Efros <powerman@sky.net.ua>]

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.