Bug 1262688 - [RFE] needs-restarting script should provide more verbose output
[RFE] needs-restarting script should provide more verbose output
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: yum-utils (Show other bugs)
Unspecified Unspecified
medium Severity low
: rc
: ---
Assigned To: Valentina Mukhamedzhanova
BaseOS QE Security Team
: FutureFeature
Depends On:
  Show dependency treegraph
Reported: 2015-09-14 02:17 EDT by Karel Srot
Modified: 2016-07-25 10:28 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
: 1262691 1431058 (view as bug list)
Last Closed: 2016-07-25 10:28:36 EDT
Type: Bug
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 Karel Srot 2015-09-14 02:17:22 EDT
Description of problem:

The needs-restarting script output only lists processes that should be restarted but doesn't provide any information about dependencies that actually caused that the restart is needed. 

  4674 : ./testprog

Please introduce a more verbose output (-v option) that would provide information about the dependencies. ATM I am using similar change for debugging purposes on various places of the code:

                if float(pkg.installtime) > float(pid_start):
                    found_match = True
+                   print "debug: %s needs restart due to usage of %s from %s" % (pid, just_fn, pkg.name)
                if just_fn in pkg.ghostlist:
                    bogon = True

but a more user friendly option would be better. E.g. to have an output as:

  4674 : ./testprog  due to /path/to/library/consumed from libtestpkg-1.0-1

or more compact

  4674 : ./testprog (/path/to/library/consumed from libtestpkg-1.0-1)

or just (as it is easy to find an appropriate package later)

  4674 : ./testprog (/path/to/library/consumed)
Comment 1 Valentina Mukhamedzhanova 2016-07-25 10:28:36 EDT
Red Hat Enterprise Linux version 6 is entering the Production 2 phase of its lifetime and this bug doesn't meet the criteria for it, i.e. only high severity issues will be fixed. Please see https://access.redhat.com/support/policy/updates/errata/ for further information.

Please feel free to open this request against Red Hat Enterprise Linux 7.

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