Blame SOURCES/psmisc-22.20-fuser-manpage-other-pids-restrict.patch

e1ee2e
diff -up ./doc/fuser.1.ori ./doc/fuser.1
e1ee2e
--- ./doc/fuser.1.ori	2017-03-14 14:28:17.318871108 +0100
e1ee2e
+++ ./doc/fuser.1	2017-03-14 14:30:49.202273564 +0100
e1ee2e
@@ -235,6 +235,15 @@ privileges.  As a consequence, files ope
e1ee2e
 other users may not be listed and executables may be classified as
e1ee2e
 mapped only.
e1ee2e
 .PP
e1ee2e
+.B fuser
e1ee2e
+cannot report on any processes that it doesn't have permission to look
e1ee2e
+at the file descriptor table for.  The most common time this problem
e1ee2e
+occurs is when looking for TCP or UDP sockets when running
e1ee2e
+.B fuser
e1ee2e
+as a non-root user.  In this case
e1ee2e
+.B fuser
e1ee2e
+will report no access.
e1ee2e
+.PP
e1ee2e
 Installing
e1ee2e
 .B fuser
e1ee2e
 SUID root will avoid problems associated with partial information, but
e1ee2e
@@ -261,15 +270,6 @@ fuser \-m /dev/sgX will show (or kill wi
e1ee2e
 even if you don't have that device configured.  There may be other
e1ee2e
 devices it does this for too.
e1ee2e
 .PP
e1ee2e
-.B fuser
e1ee2e
-cannot report on any processes that it doesn't have permission to look
e1ee2e
-at the file descriptor table for.  The most common time this problem
e1ee2e
-occurs is when looking for TCP or UDP sockets when running
e1ee2e
-.B fuser
e1ee2e
-as a non-root user.  In this case
e1ee2e
-.B fuser
e1ee2e
-will report no access
e1ee2e
-.PP
e1ee2e
 The mount \-m option will match any file within the save device as the
e1ee2e
 specified file, use the \-M option as well if you mean to specify only
e1ee2e
 the mount point.