From: "Bruce A. Locke" <blocke@shivan.org>
To: gentoo-dev@cvs.gentoo.org
Subject: Re: [gentoo-dev] why multilog?
Date: Wed Jul 11 17:02:02 2001 [thread overview]
Message-ID: <20010711190203.31eff88b.blocke@shivan.org> (raw)
In-Reply-To: <20010711185657.15a99a71.blocke@shivan.org>
Whoops... I'm sorry... I took another look and misunderstood what multilog
is doing here... How difficult would it for me to stop using multilog and
use the "old style" logging for smb, etc with their own old fashioned
files under /var/log?
On Wed, 11 Jul 2001 18:56:57 -0500
"Bruce A. Locke" <blocke@shivan.org> wrote:
>
> I've been playing around with the daemon tools package recently.
> Supervise is nice and would be handy in a server setting but I can't
> figure out why anyone would want multilog over a syslog or syslog
> replacement. The resulting log files have to be filtered to be
readable,
> they are _not_ being put into /var/log with the syslog.d stuff, etc, the
> filenames are not very human readable, there are multiple processes
> involved (including the gluelog hack). Seems like I'm loosing ease of
> use, the ability to forward logs, a standard log location, etc in
exchange
> for a poorly documented monstrocity :) What is the advantages of
> multilog? Perhaps I'm missing something :)
>
> Would it be possible to get a syslog USE keyword or equiv and have the
> supervise run scripts we create have support for it? That way if the
use
> keyword is set then people can use syslog or a syslog replacement like
> syslog-ng and people who happen to like multilog can continue using it.
>
> Just a thought... any comments?
>
> ---------------------------------------------------------------------
> Bruce A. Locke
> blocke@shivan.org
>
>
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@cvs.gentoo.org
> http://cvs.gentoo.org/mailman/listinfo/gentoo-dev
>
---------------------------------------------------------------------
Bruce A. Locke
blocke@shivan.org
next prev parent reply other threads:[~2001-07-11 23:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-11 16:57 [gentoo-dev] why multilog? Bruce A. Locke
2001-07-11 17:02 ` Bruce A. Locke [this message]
2001-07-11 19:09 ` Jerry A!
2001-07-11 19:07 ` Jerry A!
2001-07-14 8:57 ` Achim Gottinger
2001-07-14 12:29 ` Daniel Robbins
2001-07-14 20:41 ` Thomas Beaudry
2001-07-15 16:13 ` Jerry A!
2001-07-21 4:28 ` Thomas Beaudry
2001-07-21 12:49 ` Daniel Robbins
2001-07-23 7:28 ` Jerry A!
-- strict thread matches above, loose matches on Subject: below --
2001-07-24 8:44 Grant Goodyear
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=20010711190203.31eff88b.blocke@shivan.org \
--to=blocke@shivan.org \
--cc=gentoo-dev@cvs.gentoo.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