From: Alex Efros <powerman@powerman.asdfGroup.com>
Subject: Re: apache2 logs -> svlogd
Date: Mon, 13 Feb 2006 20:25:20 +0200 [thread overview]
Message-ID: <20060213182520.GE6585@home.power> (raw)
In-Reply-To: <20060213180402.GA30800@wolfpuppy.org.uk>
Hi!
On Mon, Feb 13, 2006 at 06:04:02PM +0000, Torne Wuff wrote:
> Apache can do this without any external help from FIFOs etc, just use a
> configuration like this:
I know about this. But AFAIK there some problems with this way, for ex.:
----- Forwarded message from Joshua N Pritikin <jpritikin@pobox.com> -----
Date: Wed, 7 Dec 2005 17:35:42 +0530
From: Joshua N Pritikin <jpritikin@pobox.com>
To: supervision@list.skarnet.org
Subject: svlogd choaking on lock
Hi!
I'm using svlogd for apache2 access logs. However, this is not working
too well. The problem is that when apache restarts, say a graceful USR1
restart, then it kills the old svlogd and starts a new one fast enough
that I almost always get:
svlogd: warning: unable to lock directory: /var/log/apache2/access:
temporary failure
svlogd: fatal: no functional log directories.
The error log was exhibiting the same problem but then I figured out how
to route the ErrorLog through /dev/fd/3 and then runsv took care of not
restarting svlogd. So only the access log problem remains.
Suggestions?
--
Make April 15 just another day, visit http://fairtax.org
----- End forwarded message -----
Recommended solution was put 'sleep 1' before svlogd, but for me it's a
little ugly and unreliable.
--
WBR, Alex.
next prev parent reply other threads:[~2006-02-13 18:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-13 17:38 Alex Efros
2006-02-13 18:04 ` Torne Wuff
2006-02-13 18:25 ` Alex Efros [this message]
2006-02-14 14:25 ` George Georgalis
2006-02-14 14:47 ` Joshua N Pritikin
2006-02-14 15:58 ` Alex Efros
2006-02-15 15:09 ` George Georgalis
2006-02-23 13:36 ` Dean Hall
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=20060213182520.GE6585@home.power \
--to=powerman@powerman.asdfgroup.com \
/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).