supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: Kian Kasad <kian@kasad.com>
To: supervision@list.skarnet.org
Subject: What extra logging utilities are needed with s6?
Date: Tue, 19 Jan 2021 22:56:38 -0800	[thread overview]
Message-ID: <20210120065638.embzr5fusyn6xzwl@frisbee> (raw)

[-- Attachment #1: Type: text/plain, Size: 543 bytes --]

Hi all,

I apologize if this is a "dumb" or seemingly obvious question. Logging
and monitoring are definitely my weak points when it comes to
Linux/UNIX.

In terms of logging, what exactly does s6 handle and what do I need to
handle using external programs?
I know s6 (at least how Artix Linux has it set up) will create a
directory under /var/log for each service that emits log output. Because
of this, do I need a syslog daemon like syslog-ng? And do I need a
logrotate program or does s6 handle that?

--
Kian Kasad
PGP 0x1715EEAA14DAEC14

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

             reply	other threads:[~2021-01-20  6:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-20  6:56 Kian Kasad [this message]
2021-01-20  8:21 ` Crest
2021-01-20  9:15   ` 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=20210120065638.embzr5fusyn6xzwl@frisbee \
    --to=kian@kasad.com \
    --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).