LR_RUN.IN(1)

πŸ“¦ version 2.1.1, in arch rolling

πŸ’– lr_run β€” run a Lire program & deal with the logging output πŸ’–

okay so this is lr_run.in(1), straight out of LogReport's Lire Documentation, and honestly? she's a tiny little wrapper with main character energy. let's get into it 🫢


✨ SYNOPSIS ✨

lr_run program arguments

that's it. that's the whole vibe check. πŸ’…


🌸 DESCRIPTION 🌸

okay so lr_run runs program, and then it takes program's stderr output and redirects it to logger(1). then it parses program's logging output and sets logger(1)'s flags accordingly. like, it's reading the room and adjusting the settings. iykyk. ✨

lr_run gets its configuration from sysconfdir/lire/defaults. and here's the tea on how that plays out:

  • if lr_logging_method is set to stderr, then logger(1) is not involved at all β€” logging output just gets redirected to stderr instead.
  • if lr_debug is set to the empty string, messages with loglevel debug and info get suppressed. poof. gone. πŸ™ˆ
  • and the configuration variable lr_logging_facility is what's used to find logger(1)'s facility.

πŸŽ€ NOTES πŸŽ€

program's output on stderr should be in this format, exactly:

superservice service id programname level message

and level should be one of these iconic little guys:

  • 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) for the lore. πŸ“–

id can be used to tag each Lire job, so that these can get tracked. lowkey a whole tracking system. and programname should be the name of the program which generated the log line β€” be honest about who you are, bestie. πŸ’…


πŸ¦‹ EXAMPLES πŸ¦‹

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

both slay. both valid. pick your fighter. ⭐


🌈 SEE ALSO 🌈

Documentation in the Lire User Manual β€” go read it, bestie, it's giving required reading. πŸ“š


πŸ’œ VERSION πŸ’œ

$Id: lr_run.in,v 1.23 2006/07/23 13:16:33 vanbaal Exp $

she's vintage. she's a classic. we respect her. πŸŽ€


Copyright (C) 2000-2003 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.

ok real talk for a sec β€” that "WITHOUT ANY WARRANTY" bit is not a joke, it's literally in all caps for a reason. no warranty, fr fr. 😭

🌸 THANKS 🌸

Rudi Sluijtman, for sharing some thoughts on shell scripting. we love a collaborative king 🫢✨


πŸ’« AUTHOR πŸ’«

Joost van Baal <joostvb@logreport.org>


and that's the whole page!! πŸ’– written by Joost van Baal, brought to you by Lire 2.1.1, dated 2025-09-28, and delivered to your terminal with love. now go log something responsibly, bestie. πŸŽ€πŸ¦‹πŸ’…

πŸ“¦ where this page comes from