This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-bugs] [Bug 172] xm pause/unpause misleading error

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 172] xm pause/unpause misleading error
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Mon, 19 Sep 2005 20:20:45 +0000
Delivery-date: Mon, 19 Sep 2005 20:20:50 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugs@xxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx

------- Additional Comments From pl@xxxxxxxxxx  2005-09-19 20:20 -------
Still seems a bit off to me, it's certainly an improvement, but most users would
probably expect this to behave in one of two ways:
1. see that -j is not a recognized option and print a usage statement
2. see that -j is unrecognized/unsupported and ignore it

Unless there's a good reason why something should critically run regardless of
bad options (which I don't see here) I'd opt for #1.

Configure bugmail: 
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Xen-bugs mailing list

<Prev in Thread] Current Thread [Next in Thread>