From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=5.0 tests=DKIM_ADSP_CUSTOM_MED, DKIM_INVALID,DKIM_SIGNED,FREEMAIL_FROM,MAILING_LIST_MULTI autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 14587 invoked from network); 9 Jun 2021 05:02:16 -0000 Received: from alyss.skarnet.org (95.142.172.232) by inbox.vuxu.org with ESMTPUTF8; 9 Jun 2021 05:02:16 -0000 Received: (qmail 18591 invoked by uid 89); 9 Jun 2021 05:02:38 -0000 Mailing-List: contact supervision-help@list.skarnet.org; run by ezmlm Sender: Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Received: (qmail 18584 invoked from network); 9 Jun 2021 05:02:38 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Nf7BNeXrd1G37umjHp4035vrduGVOpnMUbtzSooWWpE=; b=qNsLTkYSVEWaej0J9xFQXOYpmUFCrwv0kvL/myCaPGojuijoh2YA+ciNchL2BDDMXm T0EQxnQrgz3b9VnGnAnfExSTVtZ12nIdeeMQdnarj8IQVbHsSEBbExIZLQuAMn8SJkBz EiSnYRizxVk2zcAA3j64DyHukiDV+4QWdDuNrcFCAMzUIObbf23IvO22FDdWqmzOwPEq sSJFLGtoziqZ0ZnT9UjsNEPgOwx20EVQ1PaF+XHquy5NU0EHVBvdUS6CwjDbyNoXBPnG uYoPyjYospxsXDSt2TxgfcGC9A4IbmgheT1LlLoWHYcFWioTdrLyA1M4Mpr4ywr7hZfd IC2g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Nf7BNeXrd1G37umjHp4035vrduGVOpnMUbtzSooWWpE=; b=LaLfd/eacHS158jFy3nVJVLpPoYxdzl/I5y5c7LKO93ncPzfebXIaeylPR8QhBSCWq 7zUQhN67xrFomSRnZPLNJHEj87OlYFDvzEfGI8lZkaenkbmL2VvzeB+D74w38FLtg5fO vT0chqQnvJtJss/YSwh4q7W7V7z1jh0LWEXtzhBMOdJuUJ4KJ79djCblbSUVdD8F1I5i wmBQIYDDXYsMFU7OTdTNKOiLr2LAO08IkZDS7zM7J2u+rJ1WwIhZRIyXc2KgD4i9u8c9 JA3f7KUWK6aPdgqRMdutHXYQ0lCqG5cpfYf7Nql9eVuQEmMyy/UwqXHLRXamOb+ziuXw 9Mbg== X-Gm-Message-State: AOAM533ENRS0aN4xjyjOKRVsoxudwuDGcRXFtPA7iQttEVZUo4j4y/dd CVyXyVNnfo+ott77Vmf8W+Xfx3okkD14RlmppE55UU43bLFqkU9g X-Google-Smtp-Source: ABdhPJwPVgp+4N7S9z74QWkqPkAK62NdxRso1RDBksxgP5oGs/1ExWErETaNRPthXbaBCZq68+kb8EDFd481yvQ+Y5w= X-Received: by 2002:a5d:47a2:: with SMTP id 2mr7169198wrb.353.1623214931369; Tue, 08 Jun 2021 22:02:11 -0700 (PDT) MIME-Version: 1.0 References: <6a95462b-547f-bef8-7cc2-8d9e26b6a61d@heuristicsystems.com.au> <8e200354-c666-8ac5-92d0-963ebe7a72ef@heuristicsystems.com.au> In-Reply-To: <8e200354-c666-8ac5-92d0-963ebe7a72ef@heuristicsystems.com.au> From: Arjun D R Date: Wed, 9 Jun 2021 10:31:59 +0530 Message-ID: Subject: Re: Query on s6-log and s6-supervise To: Dewayne Geraghty Cc: supervision@list.skarnet.org Content-Type: multipart/alternative; boundary="00000000000060e0cf05c44e2d48" --00000000000060e0cf05c44e2d48 Content-Type: text/plain; charset="UTF-8" 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 < dewayne@heuristicsystems.com.au> 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. > --00000000000060e0cf05c44e2d48--