This service will be undergoing maintenance at 00:00 UTC, 2017-10-23 It is expected to last about 30 minutes
Bug 509949 - nscd rexecs itself changing the proc name to exe (by failing to follow the /proc/PID/exe symlink)
nscd rexecs itself changing the proc name to exe (by failing to follow the /p...
Status: CLOSED DUPLICATE of bug 490010
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: glibc (Show other bugs)
All Linux
low Severity medium
: rc
: ---
Assigned To: Jakub Jelinek
Depends On:
  Show dependency treegraph
Reported: 2009-07-07 01:51 EDT by Matteo Corti
Modified: 2009-07-07 04:20 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-07-07 04:20:28 EDT
Type: ---
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 Matteo Corti 2009-07-07 01:51:50 EDT
Description of problem:

nscd performs 

  /* The preparations are done.  */
  execv ("/proc/self/exe", argv);

in connections.c without following the symlink and renaming itself to 'exe'.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. start nscd
Actual results:

nscd renames itself to 'exe'

Expected results:

nscd does not rename itself to 'exe' (as on Fedora 11)

Additional info:

A correct behaviour is found for example in nscd-2.10.1-2 on Fedora 11:

  /* The preparations are done.  */
#ifdef PATH_MAX
  char pathbuf[PATH_MAX];
  char pathbuf[256];
  /* Try to exec the real nscd program so the process name (as reported
     in /proc/PID/status) will be 'nscd', but fall back to /proc/self/exe
     if readlink fails */
  ssize_t n = readlink ("/proc/self/exe", pathbuf, sizeof (pathbuf) - 1);
  if (n == -1)
    execv ("/proc/self/exe", argv);
      pathbuf[n] = '\0';
      execv (pathbuf, argv);
Comment 1 Jakub Jelinek 2009-07-07 04:20:28 EDT

*** This bug has been marked as a duplicate of bug 490010 ***

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