Bug 225064 - nscd-2.5.10 keeps dying
nscd-2.5.10 keeps dying
Status: CLOSED WORKSFORME
Product: Fedora
Classification: Fedora
Component: glibc (Show other bugs)
6
x86_64 Linux
medium Severity high
: ---
: ---
Assigned To: Jakub Jelinek
Brian Brock
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-01-28 09:34 EST by Neal Becker
Modified: 2008-08-02 19:40 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-03-19 06:13:13 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Neal Becker 2007-01-28 09:34:58 EST
Description of problem:

Running nscd @boot.  Every time I check, nscd is dead.  If I start it manually 
it seems to run OK.

I am also running networkmanager.  Is there some interaction?

There are no log messages in /var/log/{messages,dmesg} about nscd.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Jakub Jelinek 2007-01-31 09:35:11 EST
I certainly can't reproduce this, nscd works just fine on all my x86_64 FC6
machines.  Are you sure /etc/rc.d/rcX.d/S30nscd is present for your default
runlevel X?  If e.g. nscd crashed, on x86_64 you'd have a message about it
in /var/log/messages.
Comment 2 Neal Becker 2007-01-31 09:38:00 EST
/sbin/chkconfig nscd --list
nscd           	0:off	1:off	2:on	3:on	4:on	5:on	6:off
Comment 3 Neal Becker 2007-01-31 09:49:16 EST
I saw it starting on boot.

My WAG is that NetworkManager is stopping it.
Comment 4 Ulrich Drepper 2007-02-09 16:00:22 EST
Either you provide evidence that nscd is indeed dying as you claim or you take
this elsewhere and complain about NetworkManager or whatever other package. 
There are no known problems like this in nscd.

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