From: Leah Neukirchen <leah@vuxu.org>
To: peter@easthope.ca
Cc: supervision@list.skarnet.org
Subject: Re: Logging in a system with runit.
Date: Sun, 03 Nov 2024 17:26:54 +0100 [thread overview]
Message-ID: <875xp41dwx.fsf@vuxu.org> (raw)
In-Reply-To: <67278c16.5d0a0220.2b41f7.b484SMTPIN_ADDED_MISSING@mx.google.com> (peter@easthope.ca's message of "03 Nov 2024 06:43:30 -0700")
peter@easthope.ca writes:
> Searched before composing these questions.
>
> Working in Void I want to see a log to understand why a daemon isn't
> working. Therefore according to
> https://docs.voidlinux.org/config/services/logging.html
> installed socklog-void and enabled socklog-unix and nanoklogd.
> "Enabled" within the limits of my understanding.
>
> Susequently found
> https://smarden.org/runit/dependencies stating "write all logs through
> runit's logging facility. ... Therefore there's no need to depend on a
> system logging service." nanoklogd and svlogtail aren't needed to
> monitor a daemon?
Yes, if each service of your supervision tree has a $service/log
service, you don't need anything global else.
Void Linux goes a different way and uses a global syslog (socklog-unix
or rsyslog) to provide classical unified log files and to support
legacy apps using syslog(3). In this setup, $service/log is used to
push the logs into local syslog.
hth,
--
Leah Neukirchen <leah@vuxu.org> https://leahneukirchen.org/
next parent reply other threads:[~2024-11-03 16:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <67278c16.5d0a0220.2b41f7.b484SMTPIN_ADDED_MISSING@mx.google.com>
2024-11-03 16:26 ` Leah Neukirchen [this message]
2024-11-03 13:43 peter
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=875xp41dwx.fsf@vuxu.org \
--to=leah@vuxu.org \
--cc=peter@easthope.ca \
--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).