From 2abe0f2d527c7b3f6b97bd6519bf0e35a266ea68 Mon Sep 17 00:00:00 2001 From: Luke Shumaker Date: Sun, 7 Aug 2016 21:03:44 -0400 Subject: stuff --- src/grp-journal/var-log/.gitignore | 1 + src/grp-journal/var-log/README.in | 26 ++++++++++++++++++++++++++ 2 files changed, 27 insertions(+) create mode 100644 src/grp-journal/var-log/.gitignore create mode 100644 src/grp-journal/var-log/README.in (limited to 'src/grp-journal/var-log') diff --git a/src/grp-journal/var-log/.gitignore b/src/grp-journal/var-log/.gitignore new file mode 100644 index 0000000000..c3fea7424f --- /dev/null +++ b/src/grp-journal/var-log/.gitignore @@ -0,0 +1 @@ +/README diff --git a/src/grp-journal/var-log/README.in b/src/grp-journal/var-log/README.in new file mode 100644 index 0000000000..2e64fb196a --- /dev/null +++ b/src/grp-journal/var-log/README.in @@ -0,0 +1,26 @@ +You are looking for the traditional text log files in @VARLOGDIR@, and +they are gone? + +Here's an explanation on what's going on: + +You are running a systemd-based OS where traditional syslog has been +replaced with the Journal. The journal stores the same (and more) +information as classic syslog. To make use of the journal and access +the collected log data simply invoke "journalctl", which will output +the logs in the identical text-based format the syslog files in +@VARLOGDIR@ used to be. For further details, please refer to +journalctl(1). + +Alternatively, consider installing one of the traditional syslog +implementations available for your distribution, which will generate +the classic log files for you. Syslog implementations such as +syslog-ng or rsyslog may be installed side-by-side with the journal +and will continue to function the way they always did. + +Thank you! + +Further reading: + man:journalctl(1) + man:systemd-journald.service(8) + man:journald.conf(5) + http://0pointer.de/blog/projects/the-journal.html -- cgit v1.2.3-54-g00ecf