Bug 87479 - [RFE]include dependant service/package info in errata
[RFE]include dependant service/package info in errata
Product: Red Hat Network
Classification: Red Hat
Component: RHN/Other (Show other bugs)
RHN Stable
All Linux
medium Severity medium
: ---
: ---
Assigned To: rhn-dev-list
Red Hat Network Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2003-03-27 10:18 EST by Alan Fitzgerald
Modified: 2011-07-07 14:40 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2011-07-07 14:40:51 EDT
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 Alan Fitzgerald 2003-03-27 10:18:32 EST
Description of problem:
It would be very useful if the errata reports gave a listing of possible 
services that would be dependant on the updated packages.  Or packages that 
are dependant on these new packages.  I know people have trouble figuring out 
what needs to be restarted after an update.  I think this would help relieve 
the uncertainty that leads to a lot of needless restarts.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.Receive a RHN errata
2.Stare at it a while and relize, I guess I should just restart the machine

Actual Results:  Everything works.  But this is such overkill.

Expected Results:  I would restart 1 or 2 services and be sadisfied my system 
was secure and know that the uses of this box were not inconvenienced.

Additional info:
Comment 1 Chip Turner 2003-04-14 11:40:37 EDT
reassigning to mjc since this is a text/process change in the errata system
Comment 2 Mark J. Cox 2003-04-14 11:59:46 EDT
We definately need to be more consistant with the messaging of what services
are affected by a change and what needs restarting.  We're already working on
documentation for the next security guide update that explains how to work out
when to restart, and i'll see how we can add it into the errata process.  In the
meantime this is a good resource:


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