From: Charlie Brady <charlieb-supervision@budge.apana.org.au>
To: Adam Megacz <adam@megacz.com>
Cc: supervision@list.skarnet.org
Subject: Re: svlogd in funny states; reason for not integrating into runsv?
Date: Tue, 5 Jun 2007 21:22:16 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0706052110070.13856@e-smith.charlieb.ott.istop.com> (raw)
In-Reply-To: <x3hcpmexvg.fsf@nowhere.com>
On Tue, 5 Jun 2007, Adam Megacz wrote:
> 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.
It might help if you detailed exactly what "funny states" you have seen
svlogd in. And what changes it "fails to pick up". If it doesn't start at
all then perhaps what is at fault is what is supposed to start it - a run
script, for instance, might not be executable, or have bad syntax, etc.
> Is there a reason why the svlogd functionality is not integrated into
> runsv?
One reason would be historical - runit in large part is a drop-in
replacement for daemontools, and daemontools does not implement the
logging daemon in supervise. There are certainly more reasons, of course.
prev parent reply other threads:[~2007-06-06 1:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-06 0:21 Adam Megacz
2007-06-06 1:22 ` Charlie Brady [this message]
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=Pine.LNX.4.64.0706052110070.13856@e-smith.charlieb.ott.istop.com \
--to=charlieb-supervision@budge.apana.org.au \
--cc=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).