LR_RUN(1)

NAME
lr_run - run a lr program and deal with the logging output

SYNOPSIS
lr_run program arguments

DESCRIPTION
lr_run runs program, and redirects program's stderr output to logger(1). It parses programs logging output, and sets logger(1)'s flags accordingly.

lr_run gets configuration from sysconfdir/lire/defaults. In case LR_LOGGING 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 environment variable LR_FACILITY is used to find logger(1)'s facility.

NOTES
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 line.

SEE ALSO
Documentation in the Lire User Manual

VERSION
This manpage: $Id: lr_run.pod,v 1.10 2002/04/13 22:53:38 vanbaal Exp $

COPYRIGHT
Copyright (C) 2000-2002 Stichting LogReport Foundation LogReport@LogReport.org

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 http://www.gnu.org/copyleft/gpl.html or write to the Free Software Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111, USA.

THANKS
Rudi Sluijtman, for sharing some thoughts on shell scripting.

AUTHOR
Joost van Baal <joostvb@logreport.org>