Bug 209400

Summary: Bind Init Script does not create the PID file always + fix
Product: [Fedora] Fedora Reporter: Jeff Means <meaje>
Component: bindAssignee: Martin Stransky <stransky>
Status: CLOSED RAWHIDE QA Contact: Ben Levenson <benl>
Severity: medium Docs Contact:
Priority: medium    
Version: 5   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-10-05 11:17:48 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
file makes sure a PID is wriiten out to $ROOTDIR/var/run/named/named.pid before reporting sucess none

Description Jeff Means 2006-10-05 05:42:59 UTC 
Description of problem:
When killing / restarting bind (aka named) the init script will fail due to
there not being a file correctlly linked in var/run/ (named.pid)

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

How reproducible:
If running with out SE Linux it will fail to restart the named daemon as it will
not shut down the running daemon.

Steps to Reproduce:
1. Start bind / named in chroot jail (tested w/o using SE Linux)
2. init script will fail to make the file $ROOTDIR/var/run/named/named.pid but
will make the symlink /var/run/named.pid to $ROOTDIR/var/run/named/named.pid
3.
  
Actual results:
file /var/run/named.pid exists as a broken symlink

Expected results:
file /var/run/named.pid contains the PID of the running bind daemon

Additional info:
Comment 1 Jeff Means 2006-10-05 05:42:59 UTC 
Created attachment 137802 [details]
file makes sure a PID is wriiten out to $ROOTDIR/var/run/named/named.pid before reporting sucess
Comment 2 Martin Stransky 2006-10-05 11:17:48 UTC 
applied to rawhide, thanks.