Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 12 Feb 2003 09:38:35 -0800
From:      Terry Lambert <tlambert2@mindspring.com>
To:        Wes Peters <wes@softweyr.com>
Cc:        Garrett Wollman <wollman@lcs.mit.edu>, arch@FreeBSD.org
Subject:   Re: syslog.conf syntax change (multiple program/host specifications)
Message-ID:  <3E4A869B.EABBC83D@mindspring.com>
References:  <20030210114930.GB90800@melusine.cuivre.fr.eu.org> <200302120632.36583.wes@softweyr.com> <200302121411.h1CEBRSe025071@khavrinen.lcs.mit.edu> <200302121521.33506.wes@softweyr.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Wes Peters wrote:
> So you're preferring the software over the human operator.  In my world
> view, that is completely whacked.  It works fine if you're planning on
> providing a program to present the configuration to the user in a GUI or
> some such interface, but not at all if you expect the user to edit the
> configuration file as the normal mode of configuring the program.
> 
> Is THAT answer useful enough?

In the fine tradition of Open Source, you build a machine-readable
configuration file for the program, and then you leave the tool as
something for someone else to write.  And no one ever write it.

But in *theory*, your replacement for the old code is just as good
as the old code.  Heck, it's even better!

...

In terms of rolling newsyslog in: please don't.  As someone else
pointed out, there are programs that don't use syslog that do use
newsyslog (e.g. Samba, #1 answer, on the board...).

The other issue is that "revisionist history" should be a feature
of a newsyslog program; that is, if you set size limits and an old
version count limit, and you start the program up, it should "take
care of" old files.  Not something you'd want in syslog.

Finally, it's useful to replace syslog with a program that does
the same thing *and* remember program state.  Just because some
people don't follow the machine readable logging draft RFC, doesn't
mean that it can't be useful to other people (e.g. for external
SNMP instrumentation).

-- Terry

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-arch" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3E4A869B.EABBC83D>