but when using such a catch-all logger to log s6-svscan's own output
there is no need for the "rc" service to have its own logger since
everything it outputs goes into this catch-all logger.
That's the end goal. That's what s6-linux-init-1.0.0.0 does.
What you call the "rc" service is named "run
That seems to be the route that Adélie has taken. With an execline
script, /lib/s6/s6-svscanboot, configured in an /etc/inittab 'respawn'
entry. This results in a supervised s6-svscan (by sysvinit), and a
supervised catch-all logger.
Yes. I am also currently working on integrating s6-linux-init
i wonder whether s6-rc (or any other service manager or startup script)
should be started from within the supervision tree directly as
service (dir) in the scandir ?
let us assume we created a service dir "rc" or so in the otherwise
unpopulated scandir (except required loggers).
it starts s6-rc
El dom., 19 may. 2019 a las 9:57, Jeff escribió:
>
> OpenRC is known to work with s6-svscan (this is done via the
> /libexec/rc/sh/s6.sh shell script).
That is part of OpenRC's s6 integration feature, and, although on the
surface it looks like a nice thing to have, the implementation of it
launche
El dom., 19 may. 2019 a las 8:24, fungal-net escribió:
>
> [...]
> This is Adélie adelielinux.org
> installation on HD. Although it is confusing to me how they set this up
> still, after months of following its development (beta3), there is
> sysvinit on the first steps of booting then OpenRC take
> What details need to be conveyed other than "stand up", "sit down",
> and "roll over" (boot, sigpwr, sigint)?
depends on what you plan to do. for a minimal init handling SIGCHLD
(that is an interesting point indeed. is it really necessary ?
i still have to find out. would be nice if one could
On Sun, May 19, 2019 at 10:54 AM Jeff wrote:
> [...]
> On Thu, May 16, 2019 at 09:25:09PM +, Laurent Bercot wrote:
> > [...]
> > Okay, so your IPC mechanism isn't just message queues, it's a mix
> > of two different channels: message queues *plus* signals.
>
> well, no. the mechanism is SysV m
BTW:
i assume runit-init was introduced when its author wanted go get rid
of SysV init without changing runsvdir while s6-svscan's signal
handling functionality was motivated by the same desire and previous
hacks that involved running svscan directly as process #1.
this explains their authors'
On Thu, May 16, 2019 at 09:25:09PM +, Laurent Bercot wrote:
> Oh? And the other complaints haven't given you a clue?
> We are a friendly community, and that includes choosing to follow
> widely adopted threading conventions in order to make your readers
> comfortable, instead of breaking them
On Sun, May 19, 2019 at 02:57:14PM +0200, Jeff wrote:
> ... a bunch of stuff ...
Please stop breaking threads. Or if you must break threads include a
(was: blah) in the Subject: to help people's mail readers out.
--
Colin Booth
19.05.2019, 13:24, "fungal-net" :
> I am glad some of you can tell more than I can about this, and since you
> did I tried my weirdest of setups. This is Adélie adelielinux.org
> installation on HD. Although it is confusing to me how they set this up
> still, after months of following its developme
Guillermo:
>> But although I got curious what "kill -9 -1" would do to different
>> systems I don't see the usefulness of this.
>
> Since you actually went ahead and did it, and reported the results,
> for me it was interesting to see if they matched what theory says that
> would happen. They did
12 matches
Mail list logo
