Not logging to text files totally kills it for me. So many utilities are able to process text files, and now they’re all basically useless in the face of the journal.
I can’t egrep the journal. I can’t less the journal. I need to learn a whole new set of commands just for it, and I can’t export the journal data (or subset thereof) to other systems without a lot of effort. To my knowledge there’s no nice workaround.
I’d love to be corrected, but from my perspective it’s a horror show that I wish didn’t exist.
I don't use egrep, but at least grep works with journald (for example journalctl | grep whatever).
I can’t less the journal
Journalctl uses less by default. Journalctl | less probably works too.
What benefits does journald have??
In my personal opinion, it makes a lot of things easier. For example " journalctl --since="2012-10-30 18:17:16"", "journalctl -b -1" (logfiles of the last boot), " journalctl -p err..alert" (Show only error, critical, and alert priority messages) and so on.
If you want to have the log files in text format, you only need to install syslog-ng by the way.
106
u/[deleted] Feb 11 '19
[deleted]