Description of problem: It would be nice if we could see the ACTUAL full path of a binary when researching what is running more easily. Version-Release number of selected component (if applicable): all How reproducible: absolutely Steps to Reproduce: 1. ps -fp somePidId 2. 3. Actual results: shows process name, but NOT the absolute path Expected results: in MAC's OSX, you get the FULL path back Additional info: YES this can be done by ls -l /proc/somPIDId/exe but below are examples of results linux: ps -fp 14458 firebird 14458 418 0 08:11 ? 00:00:00 fb_inet_server>> mac_osx: ps -f 503 503 51434 1 0 5:46AM ?? 0:00.06 /Library/Frameworks/Firebird.framework/Resources/bin/fb_inet_servere outputs from my fedora box (same on ubuntu) and a MAC I was tracing a problem where another fb_inet_server turned out to be running from /usr/sbin causing big problems with tomcat. It was hell to find out what was going on. Showing the path to the executable would have saved hours for me. I am sure others would appreciate it.
Hello Ray, I believe 'ps -F' or "self-cooked" 'ps -o args' might cover what you are searching for. As per manpage, 'ps -f' only shows "full" info with just a command executable name (without path), which is what you are experiencing.
Many thanks Jan, It was a valiant try. I tried "-F" - with "ps -eaF" and again "ps -ea -F" Here is the latter result which does not show me where the server was running from. Note that xinetd does show as you surmised. bit fb_inet_server and grep do not show full paths. The fb_inet_server was the reason I wrote this suggestion. $ ps -ea -F | grep inet root 994 1 0 6805 2364 2 11:29 ? 00:00:00 /usr/sbin/xinetd -stayalive -pidfile /var/run/xinetd.pid root 1414 994 0 38531 10272 3 11:30 ? 00:00:00 fb_inet_server root 1421 994 0 40580 10024 3 11:30 ? 00:00:00 fb_inet_server root 1427 994 0 38531 10232 3 11:30 ? 00:00:00 fb_inet_server root 1433 994 0 38531 10004 3 11:30 ? 00:00:00 fb_inet_server root 1439 994 0 38531 10428 3 11:30 ? 00:00:00 fb_inet_server root 1445 994 0 38531 10084 3 11:30 ? 00:00:00 fb_inet_server root 1451 994 0 40580 10056 3 11:30 ? 00:00:00 fb_inet_server root 1457 994 0 38532 10512 3 11:30 ? 00:00:00 fb_inet_server root 1463 994 0 38532 10092 2 11:30 ? 00:00:00 fb_inet_server root 1469 994 0 40940 13204 2 11:30 ? 00:00:00 fb_inet_server root 1508 994 0 38531 9648 2 11:30 ? 00:00:00 fb_inet_server root 1514 994 0 38531 10244 2 11:30 ? 00:00:00 fb_inet_server ray 6877 2252 0 29286 964 0 16:50 pts/0 00:00:00 grep --color=auto inet Do I need to build one to do this?
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '24'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
still relevant
Just to be clear for WHY. I found that the system was running a process (fb_inet_server) from a directory containing a very old flakey version (I did not even know this version was still on my machine). It took immense effort to find this out. If I could have seen the full path using "ps", I would have saved a lot of time fixing the problem.
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Created attachment 1450059 [details] Enhancement proposed to upstream
So I proposed a patch to upstream. It will be incorporated into Fedora if it gets into upstream first.
Excellent, thank you Jan.
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '28'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 28 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
Still waiting on upstream merge
This message is a reminder that Fedora 30 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '30'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 30 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
FEDORA-2020-563e62fc25 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2020-563e62fc25
FEDORA-2020-88275b3477 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-88275b3477
FEDORA-2020-88275b3477 has been pushed to the Fedora 32 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-88275b3477` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-88275b3477 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-563e62fc25 has been pushed to the Fedora 33 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-563e62fc25` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-563e62fc25 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-563e62fc25 has been pushed to the Fedora 33 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2020-88275b3477 has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report.