Bug 960779

Summary: /etc/sysconfig/network-scripts/network-functions uses /var/lock/subsys/nscd which does not exist
Product: [Fedora] Fedora Reporter: Edgar Hoch <edgar.hoch>
Component: initscriptsAssignee: Bill Nottingham <notting>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: iarlyy, jonathan, lnykryn, notting, plautrba, rvokal, vpavlin
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: initscripts-9.47-1.fc19 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-06-07 04:34:26 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Edgar Hoch 2013-05-08 00:05:29 UTC
Description of problem:

Script /etc/sysconfig/network-scripts/network-functions contains a function change_resolv_conf which contains the line

[ -e /var/lock/subsys/nscd ] && /usr/sbin/nscd -i hosts; # invalidate cache

But it seems that file /var/lock/subsys/nscd which does not exist, even if nscd running. So this test never succeeds even and the nscd cache will not invalidated.

The script should use another method to test if nscd is running.


Version-Release number of selected component (if applicable):
initscripts-9.42.2-3.fc18.x86_64

How reproducible:
Always.

Steps to Reproduce:
1. Check if nscd is running. If not, start nscd.
2. Check if file /var/lock/subsys/nscd exist.
  
Actual results:
File /var/lock/subsys/nscd does not exist.

Expected results:
It is ok that file /var/lock/subsys/nscd does not exist.
But the script should use another methode for to test if nscd is running.

Comment 1 Lukáš Nykrýn 2013-05-15 10:04:02 UTC
Probably we can check existence of /var/run/nscd/socket

Comment 2 Fedora Update System 2013-05-31 08:28:15 UTC
initscripts-9.47-1.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/initscripts-9.47-1.fc19

Comment 3 Fedora Update System 2013-05-31 18:10:05 UTC
Package initscripts-9.47-1.fc19:
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing initscripts-9.47-1.fc19'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-9737/initscripts-9.47-1.fc19
then log in and leave karma (feedback).

Comment 4 Fedora Update System 2013-06-07 04:34:26 UTC
initscripts-9.47-1.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.