From the course: Linux System Engineer: Kernel Tuning and Remote Logging

Unlock the full course today

Join today to access over 22,600 courses taught by industry experts or purchase this course individually.

Understand Enterprise 7 logging

Understand Enterprise 7 logging

From the course: Linux System Engineer: Kernel Tuning and Remote Logging

Start my 1-month free trial

Understand Enterprise 7 logging

“

- [Narrator] The second method of logging data in Enterprise Linux is a service called Journald which is part of Systemd. The journal is a binary file stored in slash-var-slash-run which is a virtual file system in RAM. Everything in this file system disappears on reboot thus the journal data by default, is not persistent. Because it's in RAM, it also has a fixed size based on the amount of memory the system has. The data in the journal is structured and indexed so it can be accessed very quickly. If persistence is necessary, Journald can be configured to be persistent or even forward journal data to our Syslog. To view the journal entries, we'll use Journalctl. In a Terminal, type in: sudo-space-journalctl and hit enter. If prompted type in your password; typing Journalctl in without any Arguments gives us all Journal entries. If we want to be more specific and only show the Journal entries from the Kernel, we can specify the dash-k option. Press 'q' to quit, bring your line back and…

Contents