supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: Crest <crest@rlwinm.de>
To: supervision@list.skarnet.org
Subject: Re: What extra logging utilities are needed with s6?
Date: Wed, 20 Jan 2021 09:21:29 +0100	[thread overview]
Message-ID: <fa104e06-8f44-1137-64f3-c6021f31cf60@rlwinm.de> (raw)
In-Reply-To: <20210120065638.embzr5fusyn6xzwl@frisbee>

On 20.01.21 07:56, Kian Kasad wrote:
> 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?
If all your services support logging to stdout/stderr you can get away 
without a syslog service. Instead of a single logging service consuming 
logs from all other services s6 is designed to connect each long running 
service with its own tiny dedicated logging service.
> And do I need a logrotate program or does s6 handle that?
You don't need and external log rotation program. The s6-log utility 
includes support for log rotation and post processing and log rotation 
is enabled by default.

  reply	other threads:[~2021-01-20  8:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-20  6:56 Kian Kasad
2021-01-20  8:21 ` Crest [this message]
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=fa104e06-8f44-1137-64f3-c6021f31cf60@rlwinm.de \
    --to=crest@rlwinm.de \
    --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).