Bug 1262688

Summary: [RFE] needs-restarting script should provide more verbose output
Product: Red Hat Enterprise Linux 6 Reporter: Karel Srot <ksrot>
Component: yum-utilsAssignee: Valentina Mukhamedzhanova <vmukhame>
Status: CLOSED WONTFIX QA Contact: BaseOS QE Security Team <qe-baseos-security>
Severity: low Docs Contact:
Priority: medium    
Version: 6.7Keywords: FutureFeature
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
: 1262691 1431058 (view as bug list) Environment:
Last Closed: 2016-07-25 14:28:36 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Karel Srot 2015-09-14 06:17:22 UTC
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. 

E.g.:
  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):
                    needing_restart.add(pid)
                    found_match = True
+                   print "debug: %s needs restart due to usage of %s from %s" % (pid, just_fn, pkg.name)
                    continue
                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 14:28:36 UTC
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.