Bug 181613 - init script removed on every upgrade
Summary: init script removed on every upgrade
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: nagios
Version: 4
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Mike McGrath
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-02-15 14:11 UTC by Martin Ebourne
Modified: 2007-11-30 22:11 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-02-15 20:13:45 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Martin Ebourne 2006-02-15 14:11:04 UTC
Description of problem:
On every upgrade of this nagios package the init script is deregistered from
chkconfig.

Version-Release number of selected component (if applicable):
nagios-2.0-0.4.rc2.fc4

How reproducible:
Every time

Steps to Reproduce:
1. Install previous version of nagios
2. Upgrade to the current one
  
Actual results:
nagios has been unregistered from chkconfig and therefore will no longer
automatically start on boot.

Expected results:
nagios should still be registered in the same runlevels as before

Additional info:
The problem is the preun script:
  /sbin/service nagios stop > /dev/null 2>&1 || :
  /sbin/chkconfig --del nagios || :

This needs a check for upgrading, as in:
  if [ $1 = 0 ]; then
    /sbin/service nagios stop > /dev/null 2>&1 || :
    /sbin/chkconfig --del nagios || :
  fi

This is a standard idiom in spec files. This would be forgivable in most
packages but nothing emails me to tell me nagios is not running and I only find
out when something else fails quietly. This package really has to get this right
- doesn't anyone review these packages?

As to fixing this: because the preun script is run from the old package this
will break again (for the last time) on the next upgrade. Suggest you warn
people in the email.

Comment 1 Mike McGrath 2006-02-15 20:13:45 UTC
Damn, I noticed this on the last upgrade and completely forgot to fix it.  Its
fixed in the next release.  (Which is already built but not yet in the Extra's Repo)


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