Documentation says:
"
Signals
runit only accepts signals in stage 2.
If runit receives a CONT signal and the file /etc/runit/stopit exists
and has the execute by owner permission set, runit is told to shutdown
the system.
if runit receives an INT signal, a ctrl-alt-del keyboard request is
triggered.
"
If you read it carefully, there is NO signal for shutdown.
Or lxd should also create file /etc/runit/stopit and set permissions for
that?
Also what complexity you are talking about? runit.c is only 346 lines long.
On 14.02.2020 16:57, Casper Ti. Vector wrote:
On Fri, Feb 14, 2020 at 04:39:28PM +0300, innerspacepilot wrote:
You mean that adding few lines of code in one place is worse than many
users of many distros must configure their containers?
I can configure that myself, but I don't want every user of runit driven
container to walk this path. Is it necessary?
It adds complexity to users, and that means users will choose other
distros which just work.
The burden is just a few lines of code anyway, and user only need to
learn it once. It is also easily doable with some templating mechanism.
Also there is a huge lack of documentation about it on the net,
especially on signals that runit accepts.
<http://smarden.org/runit/runit.8.html>.
Took me less than one minute.
