docs: Note limitation of pidof find scripts (catch up)

--------------- Original Master Branch Commit Message:
pidof will miss scripts that are run a certain way due to how
they appear in procfs. This is just a note to say it might miss
them.

References:
 procps-ng/procps#17

Signed-off-by: Jim Warner <james.warner@comcast.net>
This commit is contained in:
Jim Warner 2018-04-11 00:00:00 -05:00 committed by Craig Small
parent 39980d6e31
commit fb44ecf12f

View File

@ -15,7 +15,7 @@
.\" along with this program; if not, write to the Free Software
.\" Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
.\"
.TH PIDOF 1 "24 Jul 2013" "" "User Commands"
.TH PIDOF 1 "2018-03-03" "" "User Commands"
.SH NAME
pidof -- find the process ID of a running program.
.SH SYNOPSIS
@ -60,6 +60,13 @@ At least one program was found with the requested name.
.B 1
No program was found with the requested name.
.SH BUGS
When using the \fI\-x\fP option,
.B pidof
only has a simple method for detecting scripts and will miss scripts that,
for example, use env. This limitation is due to how the scripts look in
the proc filesystem.
.SH SEE ALSO
.BR pgrep (1),
.BR pkill (1)