supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: Jeff <sysinit@yandex.com>
To: supervision@list.skarnet.org
Subject: special s6-svscan/perp(d) catch-all logger service option
Date: Thu, 25 Apr 2019 20:09:03 +0200	[thread overview]
Message-ID: <48006661556215743@iva7-8175209a746b.qloud-c.yandex.net> (raw)


hello,

i am a new subscriber to this mailing list.

i saw that daemontools-encore svscan provides an option to
specify a special catch-all logging service for svscan and its child
supervise processes:

svscan [ directory ] [ log-service ]

If the 'log-service' option is specified and the named subdirectory
exists, svscan starts the service found there and redirects its output
through it. This service is started before any other (since it is the very
important catch-all logger for (among others) svscan's own output).

it would be very nice for s6(-svscan) and perp(d) to provide such
functionality too.

this would simplify starting them directly from init(tab) (or use as init stage 2
in the case of s6) to a great extent as they would do their output redirections
by themselves and also supervise this special catch-all logging service
directly which would init free from this additional task. now init has only 
to supervise (and restart) one process (s6-svscan/perpd) instead of 2
(the additional catch-add logger) which of course is much easier to
achieve.

when using s6-svscan for init stage 2 this would also simplify the
stage 1 script greatly since it can just directly exec into stage 2
now (by using this option) without doing the output redirection
for s6-svscan by itself.

i also think that this can be achieved without too much effort
and since it is an optional feature would not break compatibility
with earlier versions and hence older scripts should still work
without requiring any changes.

kind regards.




             reply	other threads:[~2019-04-25 18:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-25 18:09 Jeff [this message]
2019-04-25 23:11 ` Laurent Bercot
2019-04-26  1:01   ` s6-svscan catch-all logger service Jeff
2019-04-26  9:45     ` Laurent Bercot
2019-04-26 16:29       ` Jeff
2019-04-26 18:45         ` Laurent Bercot
2019-04-26 19:23           ` Jeff

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=48006661556215743@iva7-8175209a746b.qloud-c.yandex.net \
    --to=sysinit@yandex.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).