From: Arjun D R <email@example.com> To: Dewayne Geraghty <firstname.lastname@example.org> Cc: email@example.com Subject: Re: Query on s6-log and s6-supervise Date: Wed, 9 Jun 2021 10:31:59 +0530 [thread overview] Message-ID: <CAHJ2E=nS07+WbCczR5LD3RjdXNzqFCKQSWnB+fxcsYCmBPVDzw@mail.gmail.com> (raw) In-Reply-To: <firstname.lastname@example.org> [-- Attachment #1: Type: text/plain, Size: 1426 bytes --] Dewayne, Thanks for the details. We already have such an implementation (multiple producers with one consumer) but still our s6-log instances are high. Many of our services require direct logger services. We can reduce the direct logger services by creating a funnel and using regex to separate the logs but that indeed is a risky and complicated process. I am just interested to confirm the memory usage of s6-log and s6-supervise processes. Thanks, Arjun On Wed, Jun 9, 2021 at 9:11 AM Dewayne Geraghty < email@example.com> wrote: > Apologies, I'd implied that we have multiple s6-supervise processes > running and their children pipe to one file which is read by one s6-log > file. > > You can achieve this outcome by using s6-rc's, where one consumer can > receive multiple inputs from producers. > > There is a special (but not unique) case where a program, such as apache > which will have explicit log files (defined in apache's config file) to > record web-page accesses and error logs, on a per server basis. Because > all the supervised apache instances can write to one error logfile, I > instructed apache to write to a pipe. Multiple supervised apache > instances using the one pipe (aka funnel), which was read by one s6-log. > This way reducing the number of (s6-log) processes. I could do the > same with the access logs and use the regex function of s6-log, but I > tend to simplicity. >
prev parent reply other threads:[~2021-06-09 5:02 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-08 9:13 Arjun D R 2021-06-08 11:04 ` Laurent Bercot 2021-06-09 2:19 ` Dewayne Geraghty 2021-06-09 3:30 ` Arjun D R 2021-06-09 8:32 ` Colin Booth 2021-06-09 11:48 ` Laurent Bercot 2021-06-10 3:54 ` Arjun D R [not found] ` <CAHJ2E=n4+bfO39LYfGaTpaqPGtPHUSy32++4t4n+PjdZz+S=Cw@mail.gmail.com> 2021-06-09 3:40 ` Dewayne Geraghty 2021-06-09 5:01 ` Arjun D R [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='CAHJ2E=nS07+WbCczR5LD3RjdXNzqFCKQSWnB+fxcsYCmBPVDzw@mail.gmail.com' \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: Query on s6-log and s6-supervise' \ /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
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).