From: Paul Sopka <psopka@sopka.ch>
To: supervision@list.skarnet.org
Subject: s6/s6-rc policy for Gentoo: The logging directory
Date: Sat, 6 Jul 2024 01:45:42 +0200 [thread overview]
Message-ID: <e3379eb6-ead1-427c-9235-8969fd59b7f9@sopka.ch> (raw)
[-- Attachment #1.1.1: Type: text/plain, Size: 847 bytes --]
The last "thread" I open for this night. I promise.
I currently have set up logging in the following way:
System supervision tree logs to to /var/log/${daemon}
User supervision tree logs got to /var/log/${USER}/${daemon}
Currently, the logging dir is hardcoded in all s6-log daemons. I want to
change that.
Concerning the user tree loggers, this is easy, the system service
starting the user tree just sets an environment variable all user tree
s6-log daemons can use.
Concerning the system tree loggers, my first idea is to set an
environment variable somewhere in the scripts s6-linux-init provides.
Is this even possible?
What would be the best place to do this?
Is there a better alternative?
Generally, I would be interested hear what you think about my choice of
logging directories.
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-05 23:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-05 23:45 Paul Sopka [this message]
2024-07-06 10:06 ` Laurent Bercot
2024-07-06 13:28 ` Paul Sopka
[not found] ` <ZoqyuyVTk4fBYm3s@sparta>
2024-07-07 15:46 ` Paul Sopka
2024-07-08 22:45 ` Peter Pentchev
2024-07-09 0:03 ` Jan Braun
2024-07-09 8:24 ` Paul Sopka
2024-07-12 13:15 ` Carlos Eduardo
2024-07-13 10:04 ` Paul Sopka
2024-07-14 15:25 ` Jan Braun
2024-07-14 20:57 ` Paul Sopka
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=e3379eb6-ead1-427c-9235-8969fd59b7f9@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).