From fb44ecf12f6e5721b0d8ead407611ae4ed6e08a2 Mon Sep 17 00:00:00 2001 From: Jim Warner Date: Wed, 11 Apr 2018 00:00:00 -0500 Subject: [PATCH] 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 --- pidof.1 | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/pidof.1 b/pidof.1 index 15b40317..1368704c 100644 --- a/pidof.1 +++ b/pidof.1 @@ -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)