ABRT-DUMP-JOURNAL-CORE(1)

💖 ABRT-DUMP-JOURNAL() 💖

---

✨ NAME ✨

okay so the whole point of abrt-dump-journal-core is to dig coredumps out of the systemd-journal and turn each one into a problem directory 🔥 it's literally the coredump whisperer 🧚

---

🎀 SYNOPSIS 🎀

abrt-dump-journal-core [-vsf] [-e]/[-c CURSOR] [-t INT]/[-T] [-d DIR]/[-D]

---

🦋 DESCRIPTION 🦋

bestie, this tool makes a problem directory for every coredump it pulls from systemd-journal 💅 it can also keep following the journal and grab coredumps the moment they happen, which is so iconic ✨

following mode picks up right where it left off, starting from the last seen cursor 🫶 if that cursor file doesn't exist yet, it starts by scanning the entire systemd-journal, or from the end if you pass -e 👀

⚠️ -c and -e are a no-go together, because both of them decide where the first message gets read from 🙅‍♀️

-e is only really useful with -f 💖 following the journal starts by reading the entire journal whenever the last seen position isn't available, so -e is the thing that changes that starting point.

---

🌸 FILES 🌸

• /var/lib/abrt/abrt-dump-journal-core.state the state file where the systemd-journal cursor for the last seen message gets saved 🧚

---

💜 OPTIONS 💜

• -v, --verbose — be more chatty 🗣️ you can stack it, so give it more than once for extra detail
• -s — send logs to syslog 📜
• -d DIR — make a brand new problem directory inside DIR for every coredump 🍓
• -D — same as -d DumpLocation, where DumpLocation is set in abrt.conf 🌈
• -e — start following systemd-journal from the end 🔚
• -t INT — throttle problem directory creation to 1 per INT second 🐢
• -T — same as -t INT, but the INT value comes from plugins/CCpp.conf ⭐
• -f — follow systemd-journal from the last seen position, if one is available 🦋

---

🫶 SEE ALSO 🫶

abrt.conf(5), journalctl(1) 💅

---

👑 AUTHORS 👑

• ABRT team 🌟

---

Signing off from ABRT-DUMP-JOURNAL() 💖✨ iykyk, and if you didn't, now you're literally one of us 🧚🌈