From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.sysutils.supervision.general/2626 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Dewayne Geraghty Newsgroups: gmane.comp.sysutils.supervision.general Subject: A better method than daisy-chaining logging files? Date: Fri, 31 May 2019 15:24:42 +1000 Message-ID: <16c909e2-9b84-63c8-7c60-380befe28f01@heuristicsystems.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="181527"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 To: supervision@list.skarnet.org Original-X-From: supervision-return-2216-gcsg-supervision=m.gmane.org@list.skarnet.org Fri May 31 07:26:09 2019 Return-path: Envelope-to: gcsg-supervision@m.gmane.org Original-Received: from alyss.skarnet.org ([95.142.172.232]) by blaine.gmane.org with smtp (Exim 4.89) (envelope-from ) id 1hWa3K-000l3M-87 for gcsg-supervision@m.gmane.org; Fri, 31 May 2019 07:26:06 +0200 Original-Received: (qmail 25606 invoked by uid 89); 31 May 2019 05:26:29 -0000 Mailing-List: contact supervision-help@list.skarnet.org; run by ezmlm Original-Sender: Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Original-Received: (qmail 25599 invoked from network); 31 May 2019 05:26:28 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=heuristicsystems.com.au; s=hsa; t=1559280282; x=1559885083; bh=8uEF+YqbWImHUQwvRckBfEOXwmp6FNvGC5nzNtTh0j0=; h=To:From:Subject:Message-ID:Date; b=WiBLmFUKEgjeovXQhWZ2RNSwPnqQx3xyBaxzRxNEKJvVrK3DBcfcfVdNg5LUGmL/4 7yJ3l9JDnLarCmgGNXUDjSa03/Fzamd7LBu2BQU30KucmyrEc2QYE3xvazPjGET9IQ XpQtTap826q0lSwWzTkH0ZGnRiM2WRW4O1+y/J546Z1M2C2hOItGs X-Authentication-Warning: b3.hs: Host noddy.hs [10.0.5.3] claimed to be [10.0.5.3] Openpgp: preference=signencrypt Content-Language: en-AU Xref: news.gmane.org gmane.comp.sysutils.supervision.general:2626 Archived-At: I'm still working the Apache problem, and I'm using s6-log to manage the logs. I just attempted to link an apache24 instance to its log files via a bundle, which isn't acceptable to s6-rc-compile. The approach attempted was to chain: 1. apache24 (longrun) and is a producer-for apache24-log 2. apache24-log (bundle) is a consumer-for apache24, with contents, the following, two longrun's for logging) 3. apache24-access-log (longrun) & apache24-error-log (longrun) Is it envisaged that s6-rc would enable something like this in the future, or will the following method remain: 1. apache24 (longrun) and is a producer-for apache24-access-log -. apache24-log (bundle) [ only for admin, though largely redundant ] 2. apache24-access-log (longrun) consumer-for apache24, producer-for apache24-error-log 3. apache24-error-log (longrun) consumer-for apache24-access-log The link between items 2 and 3 is fictional as is the absence of a connection between 1 and 3. Ideally having: apache24 as producer-for (both) apache24-access-log and apache24-error-log might be another option as it reflects reality. But this also isn't acceptable to the s6-rc-compile. This is a very simplified example as I have 6 sites to manage, and its seems wrong to complicate the setup with artificial links with s6-rc? I'm very interested to understand the reasoning. Kind regards, Dewayne