Bug 8944 - Applying 8.2.2 rpms should *NOT* turn BIND off
Summary: Applying 8.2.2 rpms should *NOT* turn BIND off
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: bind
Version: 6.1
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Bernhard Rosenkraenzer
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-01-28 17:16 UTC by Larry Fahnoe
Modified: 2008-05-01 15:37 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2000-02-03 18:06:04 UTC


Attachments (Terms of Use)

Description Larry Fahnoe 2000-01-28 17:16:43 UTC
Many people have mentioned (via bugzilla) the policy change whereby BIND is
now off by default.  I do not have a problem with the policy change.  The
issue is when I apply the RPM as an update to a system already running
BIND, the RPM should note that BIND is enabled and not disable it.  If a
person makes the choice to run BIND by enabling the service, then
subsequent RPMS should either silently honor that choice, or if this is not
possible, issue a warning stating that the service has been disabled.

If the RPM cannot be made smarter (but we all know that it can), then
minimally the documentation that suggests the installation of the RPM
should note that BIND will not be started on the next reboot.

--Larry

Comment 1 Bernhard Rosenkraenzer 2000-02-03 18:06:59 UTC
We'll change it if we need to issue another security update.
Releasing a new RPM now would cause more confusion than it would help.


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