From: Alex Efros <powerman@powerman.asdfGroup.com>
Subject: Re: apache2 logs -> svlogd
Date: Tue, 14 Feb 2006 17:58:38 +0200 [thread overview]
Message-ID: <20060214155838.GB29956@home.power> (raw)
In-Reply-To: <20060214144706.GW3065@always.joy.eth.net>
Hi!
On Tue, Feb 14, 2006 at 08:17:06PM +0530, Joshua N Pritikin wrote:
> On Tue, Feb 14, 2006 at 09:25:32AM -0500, George Georgalis wrote:
> > >Recommended solution was put 'sleep 1' before svlogd, but for me it's a
> > >little ugly and unreliable.
>
> What isn't ugly about creating named pipes? I don't think the named
> pipe solution wins the beauty contest either.
Named pipes... In short, I think named pipes is better because:
- this is universal solution which can be used for any daemon which prefer
to write log files itself, for example: Xorg :) , xdm, ntpd, emerge :) ,
iptraf, mysql, oops (webproxy), samba... maybe some of them can be
configured to use svlogd, but not all (so SINGLE UNIVERSAL UGLY solution
is much better than number of different custom more-or-less ugly
solutions)
- svlogd for named pipe supervised by runsv and won't restart with it
service - no problems with sleep 1 and so
- svlogd can be reconfigured&restarted without restarting service(apache)
- you can have many services sending their logs into same named pipe
(can't imagine how this can be used in real world yet :))
- ... anything else?
> Ultimately we may need to go beat up apache developers. ;-)
YEAH! :-)
--
WBR, Alex.
next prev parent reply other threads:[~2006-02-14 15:58 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
2006-02-14 14:25 ` George Georgalis
2006-02-14 14:47 ` Joshua N Pritikin
2006-02-14 15:58 ` Alex Efros [this message]
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=20060214155838.GB29956@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).