Linux Logging Concepts: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
Line 5: | Line 5: | ||
=Overview= | =Overview= | ||
Linux system logging is managed by two systems: [[#rsyslogd|rsyslogd]] and [[#journald|journald]], which is a component of [[systemd]]. | Linux system logging is managed by two systems: [[#rsyslogd|rsyslogd]] and [[#journald|journald]], which is a component of [[Systemd_Concepts#journald|systemd]]. | ||
=rsyslogd= | =rsyslogd= | ||
Line 13: | Line 13: | ||
=journald= | =journald= | ||
journald daemon is a component of [[systemd]]. It handles syslog, kernel, and early boot messages, as well as messages written to standard output and standard error by all services. | journald daemon is a component of [[Systemd_Concepts#journald|systemd]]. It handles syslog, kernel, and early boot messages, as well as messages written to standard output and standard error by all services. |
Revision as of 17:52, 25 June 2017
Internal
Overview
Linux system logging is managed by two systems: rsyslogd and journald, which is a component of systemd.
rsyslogd
rsyslogd comes configured by default to write logging information into files like /var/log/messages, and it can be configured to provide additional filtering, encryption and log information relaying to external systems.
journald
journald daemon is a component of systemd. It handles syslog, kernel, and early boot messages, as well as messages written to standard output and standard error by all services.