Bug 808060 - [RFE] virt-who command line option improvements
Summary: [RFE] virt-who command line option improvements
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: virt-who
Version: 6.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Radek Novacek
QA Contact: Entitlement Bugs
URL:
Whiteboard:
Depends On:
Blocks: 771481 836170
TreeView+ depends on / blocked
 
Reported: 2012-03-29 13:11 UTC by Bryan Kearney
Modified: 2016-12-01 00:30 UTC (History)
4 users (show)

Fixed In Version: virt-who-0.8-1.el6
Doc Type: Rebase: Bug Fixes and Enhancements
Doc Text:
Clone Of:
: 808061 (view as bug list)
Environment:
Last Closed: 2013-02-21 09:50:38 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2013:0374 0 normal SHIPPED_LIVE virt-who bug fix and enhancement update 2013-02-20 20:52:26 UTC

Description Bryan Kearney 2012-03-29 13:11:37 UTC 
Based on some usability discussions, we should enhance the cli command line options as follows.

1) virt-who 
Start in foreground, print errors to stderr (-d for debugging output)

2) virt-who -o
One-shot mode, exit after sending list of guests

3) virt-who -b
4) service virt-who start
Both the same: start on background (do double-fork), log to /var/log, no 
stdout/stderr
Comment 1 Radek Novacek 2012-09-26 06:23:27 UTC 
virt-who needs to be rebased to latest version.
Comment 2 Radek Novacek 2012-09-26 07:36:27 UTC 
This feature is present in virt-who-0.8-1.el6.
Comment 4 Hui Wang 2013-01-17 02:44:22 UTC 
Verified the issue, the result is PASS.
Version:
virt-who-0.8-5.el6.noarch

The command line options as following work well according the man config file.
virt-who -o -d
virt-who -b -d
virt-who -i $n -d

So change the status to verified.
Comment 6 errata-xmlrpc 2013-02-21 09:50:38 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2013-0374.html
Note You need to log in before you can comment on or make changes to this bug.