summaryrefslogtreecommitdiff
path: root/src/grp-journal/README.in
diff options
context:
space:
mode:
authorLuke Shumaker <lukeshu@sbcglobal.net>2016-09-13 21:24:07 -0400
committerLuke Shumaker <lukeshu@sbcglobal.net>2016-09-13 21:24:07 -0400
commitce31ec116f9bf4ad45952b6a200f4181fac311a3 (patch)
tree95bc9042a11e7f4773f10d72745396c9f46ed0ef /src/grp-journal/README.in
parentc73c7c774cbd1f0e778254d51da819490a333ab4 (diff)
./tools/notsd-move
Diffstat (limited to 'src/grp-journal/README.in')
-rw-r--r--src/grp-journal/README.in26
1 files changed, 26 insertions, 0 deletions
diff --git a/src/grp-journal/README.in b/src/grp-journal/README.in
new file mode 100644
index 0000000000..2e64fb196a
--- /dev/null
+++ b/src/grp-journal/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