{"id":4678,"date":"2018-06-04T19:55:16","date_gmt":"2018-06-04T15:55:16","guid":{"rendered":"https:\/\/www.howtoforge.com\/linux-pidof-command\/"},"modified":"2018-06-04T19:55:16","modified_gmt":"2018-06-04T15:55:16","slug":"linux-pidof-command-tutorial-for-beginners-5-examples","status":"publish","type":"post","link":"https:\/\/afaghhosting.net\/blog\/linux-pidof-command-tutorial-for-beginners-5-examples\/","title":{"rendered":"Linux pidof Command Tutorial for Beginners (5 Examples)"},"content":{"rendered":"

Linux command line offers a lot of utilities that work with processes. Once such tool is pidof<\/strong>, which – as the name suggests – gives you the process ID of an already executing process. In this tutorial, we will discuss the basics of pidof using some easy to understand examples.<\/p>\n

But before we do that, it’s worth mentioning that all examples here have been tested on an Ubuntu 16.04 LTS machine.<\/p>\n

Linux pidof command<\/h2>\n

As already mentioned above, the pidof command lets you find the process ID of a running program. Following is its syntax:<\/p>\n

pidof [options] command<\/p>\n

And here’s what the man page says about the tool:<\/p>\n

 Pidof finds the process id's (pids) of the named\u00a0 programs.\u00a0 It\u00a0 prints\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 those id's on the standard output. This program is on some systems used\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 in run-level change scripts, especially when the system has a\u00a0 System-V\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 like\u00a0\u00a0 rc\u00a0 structure.\u00a0 In\u00a0 that\u00a0 case\u00a0 these\u00a0 scripts\u00a0 are\u00a0 located\u00a0 in\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 \/etc\/rc?.d, where ? is the runlevel. If the system\u00a0 has\u00a0 a\u00a0 start-stop-\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 daemon (8) program that should be used instead.<\/pre>\n
Following are some Q&A-styled examples that should give you a good idea on how the tool works.<\/p>\n
Q1. How to use pidof command?<\/h2>\n
Basic usage is fairly simple – just\u00a0 pass the name of the program as input to the command. For example:<\/p>\n
pidof gedit<\/p>\n
\"How<\/a><\/p>\n
So you can see the command produced gedit’s process ID in the output.<\/p>\n
Q2. How to make pidof return only single pid?<\/h2>\n
Sometimes, you’ll see the pidof command returns multiple pids. For example, try running the pidof command with a web browser program as input.<\/p>\n
pidof firefox<\/p>\n
Following is the output produced on my system:<\/p>\n
\"pidof<\/a><\/p>\n
However, in case you want, you can force the tool to only produce a single PID in output. This can be done using the -s command line option.<\/p>\n
pidof -s firefox<\/p>\n
\"pidof<\/a><\/p>\n
Q3. How to limit output based on root directory?<\/h2>\n
If you want pidof to only return process ids that are running with the same root directory, use the -c command line option.<\/p>\n
pidof -c program_name<\/p>\n
Please note that this option is ignored for non-root users, as they will be unable to check the current root directory of processes
they do not own.<\/p>\n
Q4. How to use pidof in case of binaries kept on network file systems?<\/h2>\n
While dealing with binaries located on network-based file systems like NFS, you can use the -n command line option to make pidof command avoid using the stat system function call.<\/p>\n
pidof -n program_name<\/p>\n
Please note that the man page suggests “instead of using this option the the variable PIDOF_NETFS may be set and exported.”<\/p>\n
Q5. How pidof works internally?<\/h2>\n
Official docs say pidof is actually the same program as killall. The program behaves according to the name under which it is called. Here’s what the man page exactly says:<\/p>\n
 When pidof is invoked with a full pathname to the program it should\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 find the pid of, it is reasonably safe. Otherwise it is\u00a0 possible\u00a0 that\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 it\u00a0 returns\u00a0 pids of running programs that happen to have the same name\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 as the program you're after but are actually other programs. Note\u00a0 that\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 that\u00a0 the executable name of running processes is calculated with read?\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 link(2), so symbolic links to executables will also match.<\/pre>\n
Conclusion<\/h2>\n
The pidof command may come in handy in many situations. For example, if you want to kill a process whose PID you don’t know, you can quickly use this tool to find the process id and the process can be killed within no time. The pidof command doesn’t offer many options, and we’ve already discussed majority of them here. For more info, head to the tool’s man page<\/a>.<\/p>\n
\n
Share this page:<\/b><\/p>\n
\n\"\"<\/a>
\n\"\"<\/a>
\n\"\"<\/a>
\n\"\"<\/a>\n<\/p>\n<\/div>\n","protected":false},"excerpt":{"rendered":"
Linux command line offers a lot of utilities that work with processes. Once such tool is pidof, which – as the name suggests – gives you the process ID of an already executing process. In this tutorial, we will discuss the basics of pidof using some easy to understand examples. But before we do that, …<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[36],"tags":[],"class_list":["post-4678","post","type-post","status-publish","format-standard","hentry","category-36"],"_links":{"self":[{"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/posts\/4678","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/comments?post=4678"}],"version-history":[{"count":0,"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/posts\/4678\/revisions"}],"wp:attachment":[{"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/media?parent=4678"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/categories?post=4678"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/tags?post=4678"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}