Re: logging: drill down a bit

On 8/2/05, Michael Sweet <mike@easysw.com> wrote:
> Ben Collins-Sussman wrote:
> > ...
> > What I'm wondering is: do the existing logging subsystems provide this
> > sort of flexibility? Assuming that the messages being sent to
> > {syslogd, windows event system, apache logging system} are
> > sufficiently detailed, can these three systems be jiggered to do the
> > sort of filtering described above? If so, then I think everyone can
> > be happy.
>
> Apache can be instructed to send log data to different files based
> on the VirtualHost, Directory, and/or Location you are accessing.
>
> syslogd doesn't offer quite the same configurability - you can filter
> based on facility and log level, but that's about it.

Which syslogd? The one RedHat ships with its Linux? The one on
FreeBSD 4.x? The one on TurboLinux? The one with AIX?

The syslogd I use has full regex filtering and rules support. So it can
do a lot of wonderful things as far as what goes into what files.

NOTE - by the time a log message gets to syslogd, it is too late to get
the message into STDOUT or STDERR. However, that is controlled
in software when opening the "log" in openlog() (thus needs support
in software to set that flag) All other behaviors are controlled
from syslogd, including console output/warning/alerting (sending to
my pager, etc)

-- 
Michael Sinz               Technology and Engineering Director/Consultant
"Starting Startups"                          mailto:Michael.Sinz@sinz.org
My place on the web                      http://www.sinz.org/Michael.Sinz
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org