Hide Forgot
Description of problem: In some cases /proc/***/exe link does not have (deleted) suffix when the binary changes. Version-Release number of selected component (if applicable): [root@rhel5 ~]# uname -a Linux rhel5 2.6.18-274.el5 #1 SMP Fri Jul 8 17:36:59 EDT 2011 x86_64 x86_64 x86_64 GNU/Linux How reproducible: Install the squid package [root@localhost ~]# /etc/init.d/squid start Spouštím squid: . [ OK ] [root@localhost ~]# ps -A | grep squid 2790 ? 00:00:00 squid 2793 ? 00:00:00 squid [root@localhost ~]# cp /usr/sbin/squid /usr/sbin/squid.copy [root@localhost ~]# mv -f /usr/sbin/squid.copy /usr/sbin/squid Actual results: [root@localhost ~]# readlink /proc/2790/exe /usr/sbin/squid [root@localhost ~]# readlink /proc/2793/exe /usr/sbin/squid Expected results: As in rhel6 [root@rhel6 ~]# readlink /proc/1919/exe /usr/sbin/squid (deleted) [root@rhel6 ~]# readlink /proc/1922/exe /usr/sbin/squid (deleted) Additional info: With more simple binary #include <unistd.h> int main() {while (1) sleep(3600);} and the same steps link has (deleted) suffix. This issue causes different behavior of pidof in rhel5 and rhel6 (#760251).
Actually there is no difference in used binaries, problem is with their names. It seems that the suffix does not appear, when the name of binary is substring of the name of copy. https://bugzilla.redhat.com/show_bug.cgi?id=760251#c9
This request was not resolved in time for the current release. Red Hat invites you to ask your support representative to propose this request, if still desired, for consideration in the next release of Red Hat Enterprise Linux.
This bug/component is not included in scope for RHEL-5.11.0 which is the last RHEL5 minor release. This Bugzilla will soon be CLOSED as WONTFIX (at the end of RHEL5.11 development phase (Apr 22, 2014)). Please contact your account manager or support representative in case you need to escalate this bug.
Thank you for submitting this request for inclusion in Red Hat Enterprise Linux 5. We've carefully evaluated the request, but are unable to include it in RHEL5 stream. If the issue is critical for your business, please provide additional business justification through the appropriate support channels (https://access.redhat.com/site/support).