Logging in a system with runit.

Logging in a system with runit.

[peter]

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?

Clarification welcome, thanks,         ... Peter E.

-- 
VoIP:   +1 604 670 0140
work: https://en.wikibooks.org/wiki/User:PeterEasthope

Re: Logging in a system with runit.

[Leah Neukirchen]

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/