From: "Casper Ti. Vector" <caspervector@gmail.com>
To: supervision@list.skarnet.org
Subject: Re: A program that can get exactly the log of a supervised process?
Date: Tue, 26 Oct 2021 00:00:36 +0800 [thread overview]
Message-ID: <YXbUpNsE79FPDdSI@CasperVector> (raw)
In-Reply-To: <em5f7d56ff-18c6-4902-b5ab-21f5fd4dfc7b@elzian>
On Mon, Oct 25, 2021 at 12:37:41PM +0000, Laurent Bercot wrote:
> Another question is how to piggyback loggrep into the notification
> mechanism: if loggrep is tied to the logger and not to the service,
> it doesn't have native access to the notification pipe. That means a
> specific mechanism is needed to give it cross-service access.
As has been sketched in previous mails, make loggrep a double-forking
chainloader, where the grandparent blocks (before closing the
notification fd and then chaining) until the grandchild is ready to
accept logs (after connecting to the logger and spawning the "grep";
the latter perhaps being an awk script in most cases)?
> But it's probably the least bad way to do it, [...]
I fullly agree. This is the crux of the problem.
--
My current OpenPGP key:
RSA4096/0x227E8CAAB7AA186C (expires: 2022.09.20)
7077 7781 B859 5166 AE07 0286 227E 8CAA B7AA 186C
next prev parent reply other threads:[~2021-10-25 16:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <YXQyNQbpPZBKYLXC@caspervector>
2021-10-24 6:20 ` Laurent Bercot
2021-10-24 7:20 ` Casper Ti. Vector
[not found] ` <YXUJKWltk+OwYhtf@caspervector>
2021-10-25 12:37 ` Laurent Bercot
2021-10-25 12:57 ` Rio Liu
2021-10-25 13:26 ` Laurent Bercot
2021-10-25 16:00 ` Casper Ti. Vector [this message]
2021-10-23 16:03 Casper Ti. Vector
2023-06-22 17:44 ` Casper Ti. Vector
2023-06-22 19:39 ` Casper Ti. Vector
2023-06-22 19:43 ` Casper Ti. Vector
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=YXbUpNsE79FPDdSI@CasperVector \
--to=caspervector@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).