valeriyvdovin / rpms / systemd

Forked from rpms/systemd 4 years ago
Clone

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

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