docs: psr ps field is last run processor

The ps.1 manpage incorrectly stated that psr field showed the
processor the process was assigned to. However if the assignment
has changed but the process has not run, then the field doesn't
change.

Some digging by @srikard showed it wasn't the processor assigned
but the last one it was run on. The man page now correctly
describes psr in that way.

References:
 procps-ng/procps#187

diff --git a/ps/ps.1 b/ps/ps.1
index 8678123f9f0f06522aeb8d9c72188402a646d681..b433655f9fa37cd80cca8a2f0c2d88495da04ab5 100644 (file)
--- a/ps/ps.1
+++ b/ps/ps.1
@@ -4,7 +4,7 @@
 .\" Quick hack conversion by Albert Cahalan, 1998.
 .\" Licensed under version 2 of the Gnu General Public License.
 .\"
-.TH PS "1" "2021-03-05" "procps-ng" "User Commands"
+.TH PS "1" "2021-03-29" "procps-ng" "User Commands"
 .\"
 .\" To render this page:
 .\"    groff -t -b -man -X -P-resolution -P100 -Tps ps.1 &
@@ -1521,7 +1521,7 @@ priority of the process.  Higher number means lower priority.
 T}
 
 psr    PSR     T{
-processor that process is currently assigned to.
+processor that process last executed on.
 T}
 
 rgid   RGID    T{