Bug 1028445 - fuser doesn't report /proc/pid_number/exe as having any pid accessing it
fuser doesn't report /proc/pid_number/exe as having any pid accessing it
Product: Fedora
Classification: Fedora
Component: psmisc (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Jaromír Cápík
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2013-11-08 08:10 EST by Antoni Segura Puimedon
Modified: 2016-01-31 20:59 EST (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2015-06-29 08:51:33 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Antoni Segura Puimedon 2013-11-08 08:10:08 EST
Description of problem:
Previously (el6 and <=f19) when you called:
    fuser /proc/$$/exe
it would report all the sh processes that had been created and were alive from the executable symlinked in /proc/$$/exe.
In f20, however, the fuser output comes out empty regardless of how many processes you create.

Version-Release number of selected component (if applicable): psmisc-22.20-3.fc20.x86_64

How reproducible: 100%

Steps to Reproduce:
1. execute from bash "fuser /proc/$$/exe

Actual results:
Empty output

Expected results:
/proc/12058/exe:     12058e

Additional info:
For reference, in rhel6.4 I get:

1. ssh to the rhel6.4 machine:
➜  ~  fuser /proc/$$/exe
/proc/12058/exe:     12058e
2. ssh from another terminal to the same machine without unlogging the first ssh
➜  ~  fuser /proc/$$/exe
/proc/12146/exe:     12058e 12146e
Comment 2 Fedora End Of Life 2015-05-29 05:43:17 EDT
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 '20'.

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 20 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.
Comment 3 Fedora End Of Life 2015-06-29 08:51:33 EDT
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.