public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Jerry A! <jerry@thehutt.org>
To: gentoo-dev@cvs.gentoo.org
Subject: Re: [gentoo-dev] why multilog?
Date: Wed Jul 11 19:07:01 2001	[thread overview]
Message-ID: <20010711210516.A16705@gemini.thehutt.org> (raw)
In-Reply-To: <20010711185657.15a99a71.blocke@shivan.org>; from blocke@shivan.org on Wed, Jul 11, 2001 at 06:56:57PM -0500

On Wed, Jul 11, 2001 at 06:56:57PM -0500, Bruce A. Locke 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 :)

Actually, check out http://cr.yp.to/daemontools/multilog.html.  You can
figure out how to accomplish what you're for (log sizes/rotation/etc.)

As for the /var/log/syslog.d/current, just make that a symbolic link to
/var/log/syslog.

Multilog is part of a package for daemonizing programs.  However, it's
designed to not choke and not beat up on the system like syslog. 
Likewiese, it makes every effort to ensure that no data is lost.  Oh,
and it's much more lightweight than syslogd/klogd.  It's a good program.

Having said that, I'll be honest, I don't like it.  It's a preference
thing, not a technical issue.  I'd recommend app-admin/metalog (and not
just because I put it in the tree).

Reply to this message if you need step-by-step instructions and I'll
post them later tonight (leaving in a coupla minutes--don't have time
right now).

: 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.

Achim?

        --Jerry

name:  Jerry Alexandratos         ||  Open-Source software isn't a
phone: 703.599.6023               ||  matter of life or death...
email: jerry@thehutt.org          ||  ...It's much more important
                                  ||  than that!



  parent reply	other threads:[~2001-07-12  1:06 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
2001-07-11 19:09   ` Jerry A!
2001-07-11 19:07 ` Jerry A! [this message]
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=20010711210516.A16705@gemini.thehutt.org \
    --to=jerry@thehutt.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