Bug 215498

Summary: hald starts as daemon return 0 if it fails
Product: Red Hat Enterprise Linux 4 Reporter: Laurent Jean-Rigaud <laurent.jean-rigaud>
Component: halAssignee: Richard Hughes <rhughes>
Status: CLOSED WONTFIX QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 4.4   
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: 2012-06-20 16:04:08 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:

Description Laurent Jean-Rigaud 2006-11-14 12:33:03 UTC 
Description of problem:
I met a problem with hal daemon as it didn't start but nothing was traced
(syslog, console, service startup) ?! 
The problem reported is not why it doesn't start but why there is no trace of
error if hald fails to run.

Thanks for solution.

Version-Release number of selected component (if applicable):
hal-0.4.2-4.EL4

How reproducible:
The problem is that hald doesn't return any code different of 0 if it can't
start when daemonize.

hald --daemon=yes  (fails, by exemple if messagebus is not running)
echo $?  -> 0 

Also using service is the same : service haldaemon start --> shows [OK] but hald
is not running.

The only way to know the problem is to start interactivily hald with daemon=no
and verbose=yes .


Steps to Reproduce:
1. init 3
2. service messagebus stop
3. service hald start  -> show [OK] in place of [fail]
  
Actual results:


Expected results:
service should show [fail] and hald --daemon=yes should manage the status of
fork process (included in newer release of hal)

Additional info:
none
Comment 1 Jiri Pallich 2012-06-20 16:04:08 UTC 
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. 
Please See https://access.redhat.com/support/policy/updates/errata/

If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.