85

If I have multiple copies of the same application on the disk, and only one is running, as I can see with ps, how can I know the absolute path to distinguish it from the others?

97
% sudo ls -l /proc/PID/exe

eg:

% ps -auxwe | grep 24466
root     24466  0.0  0.0   1476   280 ?        S     2009   0:00 supervise sshd
% sudo ls -l /proc/24466/exe
lrwxrwxrwx 1 root root 0 Feb  1 18:05 /proc/24466/exe -> /package/admin/daemontools-0.76/command/supervise
  • 1
    In my system (ubuntu 14.04) you do not have to be superuser to run the ls command. – jarno Mar 5 '16 at 8:42
  • 2
    @jarno ls: cannot read symbolic link /proc/28783/exe: Permission denied -- it's not about running the ls command, it's about accessing the process info of a process not belonging to you. On my box, about 97% of all processes listed in /proc are root processes, and the others are distributed over 11 different users. – Irfy Mar 21 '16 at 12:53
14

Use:

pwdx $pid

This gives you the current working directory of the pid, not its absolute path.

Usually the which command will tell you which is being invoked from the shell:

#> which vlc
/usr/bin/vlc
  • 2
    this answer need more upvote.. – Kokizzu Jan 30 '15 at 3:02
  • 7
    @Kokizzu No, it doesn't because it doesn't answer the question at all. The which command only tells you which binary will be run if you execute the command now. The question was "which binary is already running there". Imagine for example having a dozen jdks on your computer. If you want to know for a running java process which jdk it's been taken from, which doesn't help you with that. It will only tell you which jdk it will be taken from, if you execute it now. The accepted answer is also the correct one. – noamik Feb 18 '16 at 9:05
  • An obvious way this answer is wrong: on my machine I run processes with different JDK versions and some 32bits/64bits. If I want to identify the correct jstack/jmap version for the process the answer above will not work while the accepted answer will. – Daniel Da Cunha Dec 7 '16 at 7:36
  • @Kokizzu This only answers the question, "What is the current working directory of the process $pid?" The edited post still doesn't answer the question. which merely tells "If the command is on the path, then what is it?" – John Strood Jun 5 '18 at 11:42
  • pwdx return me the absolute path of the exectuable program of the process depending on pid on redhat x64 6.3. – Nick Dong Dec 30 '18 at 6:05
12

One way is ps -ef

  • 4
    didn't work for a specific service, it just provide the relative path – Jader Dias Feb 1 '10 at 16:57
  • Helped me identify a process via the command it was started with. – jpierson Feb 9 '16 at 18:50
5
ps auxwwwe

Source:

https://serverfault.com/questions/62322/getting-full-path-of-executables-in-ps-auxwww-output

  • 1
    does not show ALL full qualified paths on my linux: "root 24466 0.0 0.0 1476 280 ? S 2009 0:00 supervise sshd " for example – akira Feb 1 '10 at 17:04
  • This is more accurate than the other answers... maybe not as useful, but more the right answer. Upvoted. – John Hunt Aug 30 '17 at 14:55
2

The quick answer is to use ps with options or the /proc filesystem info. That will usually work, but is not guaranteed. In general, there is no definite, guaranteed answer. For instance, what if the executing file is deleted during execution, so that there is no path to the file?

See the Unix FAQ for a little more detail, particularly questions 4.3 and 4.4.

2

Why does everyone expect you to know the PID? Here's the human-friendly way:

pwdx `pgrep ###process_name###`
  • The question states “as I can see with ps”, so it will probably display the PID – Scz Apr 9 '17 at 13:24
  • Ah ok true. I still find this to be a quicker one liner in many of my use cases. – moodboom Apr 9 '17 at 15:41
0

You could use

readlink /proc/$(pgrep -x -U $(id -ur) APP_NAME)/exe

or

find /proc/$(pgrep -x -U $(id -ur) APP_NAME)/exe -printf "%l\n"

to get the absolute path. PID is the process.

0

lsof is an option. You can try something like below:

lsof -p PROCESS_ID

This will list all the files opened by the process including the executable's actual location. It is then possible to add a few more awk, cut, grep etc. to find out the information that you are looking for.

As an example, I executed the following commands to identify where my 'java' process came from:

lsof -p 12345 | awk '{print $NF}' | grep 'java$'

  • How is this different than already posted answers exactly? – Pimp Juice IT Oct 9 '17 at 16:10

Your Answer

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Not the answer you're looking for? Browse other questions tagged or ask your own question.