ABRT-DUMP-JOURNAL-OOPS(1)

πŸ“¦
version 2.17.9 Β· 3 versions
, in fedora 43, fedora 44

Okay bestie, this is the manual page for ABRT-DUMP-JOURNAL() πŸŽ€, and it is giving main character energy ✨ πŸ’…

✨ NAME ✨

abrt-dump-journal-oops - Extract oops from systemd-journal πŸ¦‹

✨ SYNOPSIS ✨

abrt-dump-journal-oops [-vsoxtf] [-e]/[-c CURSOR] [-d DIR]/[-D]

✨ DESCRIPTION ✨

Okay so this tool makes a problem directory πŸ“ out of the oops it pulls from systemd-journal. It's literally giving detective πŸ•΅οΈβ€β™€οΈ vibes. It can also follow the journal and grab oopses the moment they happen, which is so iconic ngl πŸ”₯

Following starts from the last cursor it saw. If that last seen cursor file doesn't exist yet, it starts by scanning the entire sytemd-journal, or from the end if you pass the -e option 🌸


✨ FILES ✨

/etc/abrt/plugins/oops.conf This is the config file where you can turn off detection of non-fatal MCEs πŸ™ˆ

/var/lib/abrt/abrt-dump-journal-oops.state This is the state file where the systemd-journal cursor for the last message it saw gets saved πŸ’œ


✨ OPTIONS ✨

  • -v, --verbose β€” Be more chatty and verbose πŸ—£οΈ You can give it multiple times if you're obsessed.
  • -s β€” Log to syslog πŸ“œ
  • -o β€” Print the oopses it finds on standard output πŸ‘€
  • -d DIR β€” Make a brand new problem directory in DIR for every oops it finds πŸ“
  • -D β€” Same as -d DumpLocation. The DumpLocation is set in abrt.conf 🧚
  • -s CURSOR β€” Starts scanning systemd-journal from CURSOR πŸ”
  • -e β€” Starts following systemd-journal from the end 🏁
  • -x β€” Makes the problem directory world readable. Only works with -d or -D 🌈
  • -t β€” Throttles problem directory creation to 1 per second 🐒
  • -f β€” Follow systemd-journal πŸ¦‹

✨ SEE ALSO ✨

abrt-oops.conf(5), abrt.conf(5) πŸ’–

✨ AUTHORS ✨

  • ABRT team 🫢

That's the tea, bestie! ABRT-DUMP-JOURNAL() is officially ate and left no crumbs πŸ’…πŸŒΈ Now go read your oopses like the legend you are πŸ‘‘βœ¨

πŸ“¦ where this page comes from