Bug 277981

Summary: Failure message for named starting is overwritten at init time
Product: [Fedora] Fedora Reporter: Quentin Armitage <quentin>
Component: bindAssignee: Adam Tkac <atkac>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: medium    
Version: rawhideCC: ovasik
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: 2007-09-05 10:03:10 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
Patch file to stop overwriting of failure messages of startup of named none

Description Quentin Armitage 2007-09-05 08:29:53 UTC 
Description of problem: Cannot see named failed to start when invoked by init


Version-Release number of selected component (if applicable):bind-9.5.0-11.a6.fc8


How reproducible:Always


Steps to Reproduce:
1.Boot system
2.
3.
  
Actual results:
Line "Starting named:       [FAILED]" gets overwritten

Expected results: Should be able to see "Starting named:     [FAILED]


Additional info:
Problem can also be seen simply by invoking /etc/init.d/named start, and occurs
when named fails to be started via the daemon function call.
For some reason on my system, named will not start when invoked by
/etc/init.d/named start, but if /etc/init.d/named is copied to
/etc/init.d/named.new, then /etc/init.d/named.new start works. I am still
investigating this.

A patch file is attached that moves the echo command to ensure that a new line
is emitted after a failure to start named.
Comment 1 Quentin Armitage 2007-09-05 08:29:53 UTC 
Created attachment 187051 [details]
Patch file to stop overwriting of failure messages of startup of named
Comment 2 Adam Tkac 2007-09-05 08:43:49 UTC 
Patch looks fine I will include it in next build. And about your problems (you
use /etc/init.d/named.new instead /etc/init.d/named) - do you have SELinux in
enforcing mode? Because if you start named with *.new I guess it has different
SELinux context.

Adam
Comment 3 Adam Tkac 2007-09-05 10:03:10 UTC 
fixed in 9.5.0-11.3.a6