From: Bob <sysinit@yandex.com>
To: super <supervision@List.skarnet.org>
Subject: Re: emergency IPC with SysV message queues
Date: Sun, 19 May 2019 20:38:24 +0200 [thread overview]
Message-ID: <20190519183823.GD4861@panda> (raw)
In-Reply-To: <em215c8a88-d142-4c0c-88e7-42cca5581642@elzian>
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' design decisions and the different ways
both took.
prev parent reply other threads:[~2019-05-19 18:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-09 7:10 ipc in process #1 Jeff
2019-05-10 17:57 ` Laurent Bercot
2019-05-11 11:26 ` SysV shutdown util Jeff
2019-05-11 12:56 ` Laurent Bercot
2019-05-11 12:38 ` emergency IPC with SysV message queues Jeff
2019-05-11 13:34 ` Laurent Bercot
2019-05-16 15:15 ` Jeff
2019-05-16 21:25 ` Laurent Bercot
2019-05-16 21:54 ` Oliver Schad
2019-05-19 17:54 ` Jeff
[not found] ` <CALZWFRJws+eDthy8MCFj4PiVdRdRpM+afda6QAbEtYA4NT8ESQ@mail.gmail.com>
2019-05-19 19:59 ` Fwd: " Cameron Nemo
2019-05-19 20:26 ` Jeff
2019-05-19 18:38 ` Bob [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=20190519183823.GD4861@panda \
--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).