lr_run - run a Lire program and deal with the logging output
lr_run program arguments
lr_run runs program, and redirects program’s stderr output to
logger(1). It parses programs logging output, and sets logger(1)’s
lr_run gets configuration from sysconfdir/lire/defaults. In case
’lr_logging_method’ is set to ’stderr’, logger(1) is not involved:
logging output gets redirected to stderr. In case ’lr_debug’ is set to
the empty string, messages with loglevel debug and info get suppressed.
The configuration variable ’lr_logging_facility’ is used to find
program’s output on stderr should be in format superservice service id
programname level message. level should be one of: emerg (system is
unusable), alert (action must be taken immediately), crit (critical
conditions), err (error conditions), warning (warning conditions),
notice (normal, but significant, condition), info (informational
message), debug (debug-level message). See syslog(3).
id can be used to tag each Lire job, so that these can get tracked.
programname should be the name of the program which generated the log
To process a Postfix log and display the report as text, use
$ lr_run lr_log2report postfix < /var/log/mail.log
To process a Postfix log and create the report in HTML (packed up in a
tar archive), use:
$ lr_run lr_log2report -o html postfix < /var/log/mail.log > postfix.tar
Documentation in the Lire User Manual
$Id: lr_run.in,v 1.23 2006/07/23 13:16:33 vanbaal Exp $
Copyright (C) 2000-2003 Stichting LogReport Foundation
This program is free software; you can redistribute it and/or modify it
under the terms of the GNU General Public License as published by the
Free Software Foundation; either version 2 of the License, or (at your
option) any later version.
This program is distributed in the hope that it will be useful, but
WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
General Public License for more details.
You should have received a copy of the GNU General Public License along
with this program (see COPYING); if not, check with
Rudi Sluijtman, for sharing some thoughts on shell scripting.
Joost van Baal <email@example.com>