From: Jeff <sysinit@yandex.com>
To: supervision <supervision@list.skarnet.org>
Subject: Runit
Date: Fri, 03 May 2019 04:15:00 +0200 [thread overview]
Message-ID: <11603811556849700@myt5-262fb1897c00.qloud-c.yandex.net> (raw)
In-Reply-To: <CADQ2Nw_3hGEhFtY1cQptDL3LQJOPNyNQ0ax8zEF=PTi1PDcmmA@mail.gmail.com>
>> If something kills runsvdir, then runit immediately enters
>> stage 3, and reboots the system. This is an acceptable response
>> to the scanner dying, but is not the same thing as supervising
>> it. If runsvdir's death is accidental, the system goes through
>> an unnecessary reboot.
>
> If the /etc/runit/2 process exits with code 111 or gets killed by a
> signal, the runit program is actually supposed to respawn it,
> according to its man page. I believe this counts as supervising at
> least one process, so it would put runit in the "correct init" camp :)
>
> There is code that checks the 'wstat' value returned by a
> wait_nohang(&wstat) call that reaps the /etc/runit/2 process, however,
> it is executed only if wait_exitcode(wstat) != 0. On my computer,
> wait_exitcode() returns 0 if its argument is the wstat of a process
> killed by a signal, so runit indeed spawns /etc/runit/3 instead of
> respawning /etc/runit/2 when, for example, I point a gun at runsvdir
> on purpose and use a kill -int command specifying its PID. Changing
> the condition to wait_crashed(wstat) || (wait_exitcode(wstat) != 0)
> makes things work as intended.
that is again one of several runit problems. among them:
- see above
- no setsid(2) for child procs by default in "runsv"
- having only runsv managing the log pipe.
- runit-init requires rw fs access without the slightest need
(setting the +x bit of the /etc/runit/(stopit,reboot) files
which could indeed reside on a tmpfs in /run and be
symlinks have symlinks pointing to them (that is done in
Void Linux)
- problems with log files while bringing down the system.
i never encountered that with daemontools-encore, perp(d)
and s6.
so it is a quite dated project that clearly shows its age.
i would recommend against using it at all (except its
"chpst" and "utmpset" utilities).
prev parent reply other threads:[~2019-05-03 2:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-29 21:33 further claims Jeff
2019-04-30 8:56 ` Laurent Bercot
2019-05-01 23:09 ` Guillermo
2019-05-02 0:30 ` Colin Booth
2019-05-03 2:44 ` ToyBox oneit Jeff
2019-05-05 2:07 ` ToyBox init Jeff
2019-05-03 2:15 ` Jeff [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=11603811556849700@myt5-262fb1897c00.qloud-c.yandex.net \
--to=sysinit@yandex.com \
--cc=supervision@list.skarnet.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).