Bug 238113 - Wrong init script
Wrong init script
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: hal (Show other bugs)
5.0
All Linux
low Severity low
: rc
: ---
Assigned To: Richard Hughes
:
Depends On:
Blocks: 237789 238114 238115
  Show dependency treegraph
 
Reported: 2007-04-27 04:50 EDT by Michal Marciniszyn
Modified: 2014-02-10 18:02 EST (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-03-30 04:32:42 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Comment 2 Richard Hughes 2009-01-20 06:07:54 EST
Michal, does the init file look okay upstream? http://cgit.freedesktop.org/hal/tree/hald/haldaemon.in
Comment 3 Zack Cerza 2009-03-24 13:11:09 EDT
Whoa. Making comment #0 private because of links to intranet.corp.

Also, ack.
Comment 4 Zack Cerza 2009-05-04 15:02:09 EDT
(In reply to comment #2)
> Michal, does the init file look okay upstream?
> http://cgit.freedesktop.org/hal/tree/hald/haldaemon.in  

No. From the upstream script:

# Sanity checks.
[ -x @sbindir@/hald ] || exit 0

is the problem.
Comment 5 Richard Hughes 2009-05-12 07:54:19 EDT
(In reply to comment #4)
> (In reply to comment #2)
> > Michal, does the init file look okay upstream?
> > http://cgit.freedesktop.org/hal/tree/hald/haldaemon.in  
> 
> No. From the upstream script:
> 
> # Sanity checks.
> [ -x @sbindir@/hald ] || exit 0
> 
> is the problem.  

Can I just change this to || exit 1, or should the line be removed altogether? I don't see how the init.d script could be installed, but not /usr/sbin/hald, as they are in the same package. It seems an odd check.

I can keep this for 5.4, or punt it to 5.5 as it's not ever triggered unless you've got a very broken system.
Comment 6 Richard Hughes 2009-05-12 11:18:27 EDT
Quite a few of the other init scripts have the same sanity check as hal, exiting with status zero.
Comment 7 Zack Cerza 2009-05-12 13:29:09 EDT
Changing it to exit 1 would be fine. I agree, this is a pedantic bug report. It'd be a good idea to fix the rest of the init scripts, as exiting 0 is the wrong thing to do, but... as you said, I'm not sure that if you managed to hit this bug, the exit code will be anywhere near the top of your list of things to care about.
Comment 14 errata-xmlrpc 2010-03-30 04:32:42 EDT
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2010-0256.html

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