From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=MAILING_LIST_MULTI autolearn=ham autolearn_force=no version=3.4.4 Received: from alyss.skarnet.org (alyss.skarnet.org [95.142.172.232]) by inbox.vuxu.org (Postfix) with SMTP id 04C3D2439B for ; Thu, 11 Jul 2024 17:40:07 +0200 (CEST) Received: (qmail 1965 invoked by uid 89); 11 Jul 2024 15:40:33 -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 1958 invoked from network); 11 Jul 2024 15:40:33 -0000 From: "Laurent Bercot" To: "Paul Sopka" , supervision@list.skarnet.org Subject: Re: s6/s6-rc policy for Gentoo: logging settings Date: Thu, 11 Jul 2024 15:40:06 +0000 Message-Id: In-Reply-To: <6813d7f9-3333-416f-a24e-a3f655726853@sopka.ch> References: <6813d7f9-3333-416f-a24e-a3f655726853@sopka.ch> Reply-To: "Laurent Bercot" User-Agent: eM_Client/9.2.2258.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable >Should every s6-log daemon have it's own config file or shall they all sha= re one? What kind of stuff are you putting in the config file? Is it just a template for a logging script? >Is there any general issue with the global env's from s6-linux-init's env= directory, which makes sourcing the same config file in every s6-log script = a better choice for a global config? The global environment defined in s6-linux-init applies to *all* processes in the system. It's not nice to pollute it with stuff that would only apply to a pretty restricted subset of all the processes on the machine. Source your config file in every logger run script you have, and leave the global environment alone. There will be no performance issue. For more configurability, you could e.g. have a default logging=20 template hardcoded in your run scripts, that you could override via a service- specific configuration file. -- Laurent