Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 7031 - bind-8.2.2-P3-0.5.2 and -0.4.2 initscripts broken
bind-8.2.2-P3-0.5.2 and -0.4.2 initscripts broken
Product: Red Hat Linux
Classification: Retired
Component: bind (Show other bugs)
All Linux
medium Severity high
: ---
: ---
Assigned To: Bernhard Rosenkraenzer
Depends On:
  Show dependency treegraph
Reported: 1999-11-15 17:50 EST by Jim Knoble
Modified: 2008-05-01 11:37 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 1999-11-21 06:25:41 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jim Knoble 1999-11-15 17:50:16 EST
The initscript included in the bind-8.2.2_P3-0.5.2 security update
includes the following chkconfig comment:

  $ grep chkconfig /etc/rc.d/init.d/named
  # chkconfig: - 55 45

Unfortunately, this causes the `chkconfig --add' run from the
postinstall script to add the following initscript links:

  $ ls -1 /etc/rc.d/rc?.d/*named*

This effectively disables the named service on the next system reboot
after installing the security update.

The -0.4.2 package for Red Hat Linux 4.2 includes the same symlinks:

  $ rpm -ql bind |grep rc\.d

and has the same effect.

Also, the version number of the package is misleading, since it
actually appears to include patch4, but is named ..._P3-....

Recommend fixing the initscript problem, grabbing the recent patch5,
and rereleasing the package.
Comment 1 Bernhard Rosenkraenzer 1999-11-21 06:25:59 EST
P5 is in Raw Hide; updates for older releases are done only for major security
You can download the SRPM and recompile, though.
The chkconfig line is there to prevent bind from being started until someone
created a config file. I'll change it in the next version.

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