From 9cf3ae98df0d71b2d45135ade1293d4ed0c289a7 Mon Sep 17 00:00:00 2001 From: Masatake YAMATO Date: Sun, 7 Aug 2022 05:04:06 +0900 Subject: [PATCH] lsfd.1.adoc: write about how pidfds are represented in NAME column Signed-off-by: Masatake YAMATO --- misc-utils/lsfd.1.adoc | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) 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. -- 2.47.3