From: Adam Megacz <adam@megacz.com>
To: supervision@list.skarnet.org
Subject: svlogd in funny states; reason for not integrating into runsv?
Date: Tue, 05 Jun 2007 17:21:23 -0700 [thread overview]
Message-ID: <x3hcpmexvg.fsf@nowhere.com> (raw)
I've found runsv to be exceptionally reliable in terms of noticing
changes in /var/service/ and adapting its behavior accordingly.
Really solid.
Unfortunately, I have not found svlogd to be as robust. It often gets
into funny states or fails to pick up changes -- or just never starts
altogether. This might actually be runsv's fault rather than svlogd's
fault; I guess I'm just saying that the management of the "logging
process" is not as amazingly solid as the management of the "service
process".
Is there a reason why the svlogd functionality is not integrated into
runsv? It seems that as the parent of the service process, runsv is
in the ideal position to gather and log the process' output. This
would also keep the process table/tree a lot cleaner; only one
runit-related process per service rather than two.
- a
--
PGP/GPG: 5C9F F366 C9CF 2145 E770 B1B8 EFB1 462D A146 C380
next reply other threads:[~2007-06-06 0:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-06 0:21 Adam Megacz [this message]
2007-06-06 1:22 ` Charlie Brady
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=x3hcpmexvg.fsf@nowhere.com \
--to=adam@megacz.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).