From: Masatake YAMATO <yamato@redhat.com>
Date: Sat, 6 Aug 2022 20:04:06 +0000 (+0900)
Subject: lsfd.1.adoc: write about how pidfds are represented in NAME column
X-Git-Tag: v2.39-rc1~550^2
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=9cf3ae98df0d71b2d45135ade1293d4ed0c289a7;p=thirdparty%2Futil-linux.git

lsfd.1.adoc: write about how pidfds are represented in NAME column

Signed-off-by: Masatake YAMATO <yamato@redhat.com>
---

diff --git a/misc-utils/lsfd.1.adoc b/misc-utils/lsfd.1.adoc
index 21e25561e0..8ebabe3251 100644
--- a/misc-utils/lsfd.1.adoc
+++ b/misc-utils/lsfd.1.adoc
@@ -181,6 +181,24 @@ Access mode (rwx).
 
 NAME <``string``>::
 Name of the file.
+//
+// It seems that the manpage backend of asciidoctor has limitations
+// about emitting text with nested face specifications like:
+//
+//   `_u_` p
+//
+// Not only u but also p is decorated with underline.
+//
+For the most of all files, *lsfd* extracts their names
+from ``/proc/``_pid_``/fd/``_fd_ or ``/proc/``_pid_``/map_files/``_region_.
++
+Some files have special formats and information sources:
++
+pidfd:::
+pidfd: pid=_TARGET-PID_ comm=_TARGET-COMMAND_ nspid=_TARGET-NSPIDS_
++
+*lsfd* extracts _TARGET-PID_ and _TARGET-NSPIDS_ from
+``/proc/``_pid_``/fdinfo/``_fd_.
 
 NLINK <``number``>::
 Link count.