REPORTER-PRINT(1)

💅 reporter-print — the manual page, bestie edition

ok so this is reporter-print(1), straight out of the LIBREPORT MANUAL. she's a little unix girlie whose whole personality is printing problem info to stdout or to a FILE. iconic behaviour tbh.

---

✨ NAME ✨

reporter-print — prints problem information to standard output or FILE. that's it. that's the whole job. and she does it slayfully 🎀

---

🌈 SYNOPSIS 🌈

reporter-print [-v] [-d DIR] [-o FILE] [-a yes/no] [-r]

like look at her. five little flags. a whole lewk. 💅

---

💖 DESCRIPTION 💖

okay so the tool reads the problem directory DIR and prints its text representation to stdout or to a specified FILE. lowkey simple, highkey useful. no cap. ✨

🦋 Integration with ABRT events 🦋

reporter-print can be used as a reporter, to allow users to report problems by writing them to a file. fr fr, that's the vibe. example moment:

EVENT=report  reporter-print -o "${Log_File:-/tmp/abrt.log}"

not me putting the example in a code block and everything. you're welcome bestie 🫶

---

🎀 OPTIONS 🎀

• -d DIR — path to problem directory. that's where the problem lives. go off.
• -v — be more verbose. and the way that it can be given multiple times?? obsessed. stack those -vs like bracelets. 💜
• -o FILE — output file. the FILE. the destination. the main character of the output world.
• -a yes/no — if -o FILE is specified, this controls whether FILE is appended to, or overwritten. (default: no) ⚠️ yes this means by default she's overwriting. be aware. she's not sorry.
• -r — add a record to reported_to in DIR which specifies that this problem was reported. some tools use this to differentiate between problems which were and weren't yet reported. very "not me filing the paperwork" of her. 💀

⭐ Output format ⭐

the output is designed to be machine-parsable. so like. robots can read it. slay for the robots. 🤖✨

the elements which have only one line are printed in the form:

NAME:<whitespace>VALUE

elements which have more than one line are printed in the form:

NAME:
:LINE1
:LINE2
:LINE3

output may contain empty lines for better readability. yes the blank lines are intentional. she's not being weird, she's being readable. 🍓

---

🔥 SEE ALSO 🔥

• print_event.conf(5) — go read this one too bestie, iykyk 👑

---

👑 AUTHORS 👑

• ABRT team 🙌

---

and that's the whole thing!! this page is from LIBREPORT 2.17.15, dated 07/15/2024 — so like, she's got lore, she's got a version number, she's got a date. periodt. 💖✨🎀🦋🌸🫶