From: Paul Sopka <psopka@sopka.ch>
To: supervision@list.skarnet.org
Subject: s6/s6-rc policy for Gentoo: logging settings
Date: Thu, 11 Jul 2024 17:20:27 +0200 [thread overview]
Message-ID: <6813d7f9-3333-416f-a24e-a3f655726853@sopka.ch> (raw)
[-- Attachment #1.1.1: Type: text/plain, Size: 684 bytes --]
I have another basic decision to make, on which I am interested to hear
everybody's opinion.
Should every s6-log daemon have it's own config file or shall they all
share one?
My initial instinct on this was to put the global logging settings into
the env directory of s6-linux-init to have all of them available to
every logging daemon.
This would remove the overhead of having each of the s6-log scripts
source a config file.
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?
Thank you for your input.
Paul
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3195 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
next reply other threads:[~2024-07-11 15:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-11 15:20 Paul Sopka [this message]
2024-07-11 15:40 ` Laurent Bercot
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=6813d7f9-3333-416f-a24e-a3f655726853@sopka.ch \
--to=psopka@sopka.ch \
--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).