Qjournalctl
Version: 0.4 Web: www.bit.ly/2BtL0Th
It was not long ago that Systemd was considered highly controversial, a non-Unix-way technology, but it would be unfair nowadays to deny that Red Hat, the company behind Systemd, has finally succeeded at pushing its pet project into mainstream Linux distros. It is not a question of how much you like Systemd, but rather how you can get more use out of it. Qjournalctl is a fantastic helper tool, especially if you preferred to ignore the standard functionality of Systemd in the past. Qjournalctl is a graphical front end to the $ jornalctl command, which in turn is quite useful in the right hands. This time you don’t need to know the command-line-fu in order to be a pro, thanks to easily accessible features of Qjournalctl. The application is a piece of cake: it has just three buttons that can show you the current boot log, list all available (recorded) boots, and display the current boot log. The first button reveals a separate window where the familiar systemd messages are printed in the lower part. But look above and check out that slider! Drag it back and forth to limit the message output by their priority. That said, when the slider is in the far-right position, you will see the complete longread, but when you drag it leftward, the list get filtered down consequently to notices, warnings, errors and alerts only.
It’s impossible to underestimate the usefulness of Qjournalctl’s capabilities, as not every Linux user knows how to achieve these sorts of result with grep, or dig out some less known Systemd features. Let’s also point out that with Qjournalctl you can limit the output by a range of dates, and also see the list of all boots ever recorded. This is a simplest way to find out if or when your computer has been turned on without your attendance. If you feel curious about the boot process of your Linux system, using Qjournalctl will be a perfect entry point before you start spending the time get to know Systemd more deeply.
“Drag the slider back and forth to limit the message output by their priority”