valeriyvdovin / rpms / systemd

Forked from rpms/systemd 4 years ago
Clone

Blame SOURCES/0283-man-clarify-what-happens-when-journalctl-is-called-w.patch

803fb7
From a4f12d4849daed23651ab3c23b5ff830aa32b2a0 Mon Sep 17 00:00:00 2001
803fb7
From: Michal Sekletar <msekleta@redhat.com>
803fb7
Date: Wed, 3 Feb 2016 10:38:29 +0100
803fb7
Subject: [PATCH] man: clarify what happens when journalctl is called with
803fb7
 devpath
803fb7
803fb7
Cherry-picked from: 3cea8e06e45fc1757de8f74da29fb5fb181db4eb
803fb7
Related: #947636
803fb7
---
803fb7
 man/journalctl.xml | 10 ++++++++--
803fb7
 1 file changed, 8 insertions(+), 2 deletions(-)
803fb7
803fb7
diff --git a/man/journalctl.xml b/man/journalctl.xml
803fb7
index 2764f66ed..0981fba72 100644
803fb7
--- a/man/journalctl.xml
803fb7
+++ b/man/journalctl.xml
803fb7
@@ -91,8 +91,14 @@
803fb7
       paths may be specified. If a file path refers to an executable
803fb7
       file, this is equivalent to an <literal>_EXE=</literal> match
803fb7
       for the canonicalized binary path. Similarly, if a path refers
803fb7
-      to a device node, this is equivalent to a
803fb7
-      <literal>_KERNEL_DEVICE=</literal> match for the device.</para>
803fb7
+      to a device node then match is added for the kernel name of the
803fb7
+      device (<literal>_KERNEL_DEVICE=</literal>). Also, matches for the
803fb7
+      kernel names of all the parent devices are added automatically.
803fb7
+      Device node paths are not stable across reboots, therefore match
803fb7
+      for the current boot id (<literal>_BOOT_ID=</literal>) is
803fb7
+      always added as well. Note that only the log entries for
803fb7
+      the existing device nodes maybe queried by providing path to
803fb7
+      the device node.</para>
803fb7
 
803fb7
       <para>Additional constraints may be added using options
803fb7
       <option>--boot</option>, <option>--unit=</option>, etc, to