From: Guillermo <gdiazhartusch@gmail.com>
To: Supervision <supervision@list.skarnet.org>
Subject: Re: Some suggestions on old-fashioned usage with s6 2.10.x
Date: Fri, 29 Jan 2021 14:27:10 -0300 [thread overview]
Message-ID: <CADQ2Nw9xgsxfTWS+OMxph8mNu+wQ-cDX=sXS1MEawnt+rz_kTA@mail.gmail.com> (raw)
In-Reply-To: <YBN7zfp/MmbcHOCF@CasperVector>
El vie, 29 ene 2021 a las 0:07, Casper Ti. Vector escribió:
>
> Not using s6-linux-init has never been an explicit goal, [...]
>
> Currently I do not understand the `s6-linux-init-shutdown(d)' way
> well, so the old-fashioned way is retained at least for now, [...]
Forgive me if I'm misunderstanding aspects of the architecture, but
jugdging from a quick look at the Git repository, I *think* that you
could depend on s6-linux-init (the package):
* You could replace /etc/slew'/init/rc.boot with s6-linux-init (the
program), or a wrapper script around it. s6-linux-init does more or
less the same as the current script, except running load_clock.rc
(which you could do in /etc/slew'/init/rc.init).
* You could move the current /etc/slew/run to
/etc/s6-linux-init/current/run-image when installing slew. I'm not
sure what skalibs' hiercopy() would do if the latter is just a symlink
to the former.
* You could replace /etc/slew'/init/rc.halt with a service directory
for s6-linux-init-shutdownd in /etc/slew'/run/service, just like you
do now for the catch-all logger.
s6-linux-init-shutdownd does more or less the same as the current
script, except running save_log.rc, save_clock.rc and calling swapoff.
You can move that to /etc/slew'/init/rc.fin, or
/etc/s6-linux-init/current/rc.shutdown.final if you must do some of it
after killing all processes and unmounting filesystems.
* You could symlink /etc/s6-linux-init/current/rc.{init,shutdown} to
/etc/slew'/init/rc.{init,fin}, perhaps with some minimal
modifications.
* You could replace calls to s6-svscanctl in
/etc/slew'/run/service/.s6-svscan/SIG* with calls to s6-linux-init-hpr
if you want to be able to do e.g. 'busybox poweroff''.
* You could replace /etc/slew'/run/service/.s6-svscan/finish with
something simpler, instead of being a symlink to
/etc/slew/init/rc.halt.
G.
next prev parent reply other threads:[~2021-01-29 17:27 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-28 10:08 Casper Ti. Vector
2021-01-28 11:09 ` Casper Ti. Vector
2021-01-28 14:05 ` Casper Ti. Vector
2021-01-29 1:41 ` Guillermo
2021-01-29 3:06 ` Casper Ti. Vector
2021-01-29 17:27 ` Guillermo [this message]
2021-01-29 17:39 ` Guillermo
[not found] ` <YBN7zfp/MmbcHOCF@caspervector>
2021-01-29 9:57 ` Laurent Bercot
2021-01-29 14:33 ` Casper Ti. Vector
[not found] ` <YBQcwHN1L/N2dedx@caspervector>
2021-01-29 15:48 ` Laurent Bercot
2021-01-31 7:49 ` stage2 as a service [was: Some suggestions on old-fashioned usage with s6 2.10.x] s.karrmann
2021-01-31 10:25 ` Laurent Bercot
2021-01-31 20:51 ` stage2 as a service Stefan Karrmann
2021-02-01 10:35 ` Laurent Bercot
2021-02-15 8:36 ` Some suggestions on old-fashioned usage with s6 2.10.x Casper Ti. Vector
[not found] ` <YCoykUYGXVt+BAT9@caspervector>
[not found] ` <em949fd937-c7bc-43db-9b49-3cc235b8f2ad@elzian>
2021-02-16 8:53 ` Casper Ti. Vector
[not found] <YBKNJEuGeYag91Q1@caspervector>
2021-01-28 17:21 ` Laurent Bercot
2021-01-28 19:08 ` Roy Lanek
2021-01-28 19:55 ` Casper Ti. Vector
[not found] ` <YBMWuUCUTVjUNinQ@caspervector>
2021-01-29 0:07 ` Laurent Bercot
2021-01-29 2:44 ` Casper Ti. Vector
[not found] ` <YBN2p2UkIiP8lMQy@caspervector>
2021-01-29 9:36 ` Laurent Bercot
2021-02-15 14:58 Laurent Bercot
2021-02-15 14:59 ` Laurent Bercot
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='CADQ2Nw9xgsxfTWS+OMxph8mNu+wQ-cDX=sXS1MEawnt+rz_kTA@mail.gmail.com' \
--to=gdiazhartusch@gmail.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).