The journal has been introduced as the natural way to manage logs now that systemd takes care of all the output of daemons. > If you are wondering what the jou

The journal has been introduced as the natural way to manage logs now that systemd takes care of all the output of daemons. > If you are wondering what the journal is, here's an explanation in a few words to get you up to speed: the journal is a component of systemd, that captures Syslog messages, Kernel log messages, initial RAM disk and early boot messages as well as messages written to STDOUT/STDERR of all services, indexes them and makes this available to the user. While syslogd and Co. just take care of moving the debug statements from RAM to the disk or to a network device, the journal is meant from the beginning as an interface for querying the logs, for example $ journalctl -u httpd --since=00:00 --until=9:30 [1] http://0pointer.de/blog/projects/journalctl.html http://0pointer.de/blog/projects/journalctl.html