Improve systemd introduction

This clarifies that services that use systemd no longer place their logs
in plain text files.
This commit is contained in:
Ankur Sinha (Ankur Sinha Gmail) 2019-04-05 12:17:51 +01:00
parent 9e9c0490f5
commit e8b87f113e
No known key found for this signature in database
GPG key ID: F8D8C0BEBAC898BD

View file

@ -1,14 +1,13 @@
[id='viewing-logs in Fedora']
= Viewing logs in Fedora
Fedora uses https://freedesktop.org/wiki/Software/systemd/[systemd] which provides the `journalctl` tool to view various logs generated by system commands.
Log files contain messages about the system, including the kernel, services, and applications running on it.
There are different log files for different information.
For example, there is a default system log file, a log file for security messages, and a log file for cron tasks, this is an important task when you try to find any class of problem in your system and help you to resolve any issue.
These contain information that helps troubleshoot issues, or simply monitor system functions.
Fedora uses the https://freedesktop.org/wiki/Software/systemd/[systemd] system and service manager.
With systemd, messages for most services are now stored in the systemd journal which is a binary file that must be accessed usinng the `journalctl` command.
Most log files are located in the `/var/log/` directory.
In Fedora, there are two ways to open the log files:
System tools that do not use systemd for their logs continue to place them as plain text files in the `/var/log/` directory.
In Fedora, there are two ways of accessing system logs:
* The command line
* A GUI applications