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

http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=172





------- 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: 
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-bugs

<Prev in Thread]	Current Thread	[Next in Thread>
[Xen-bugs] [Bug 172] xm pause/unpause misleading error, bugzilla-daemon [Xen-bugs] [Bug 172] xm pause/unpause misleading error, bugzilla-daemon [Xen-bugs] [Bug 172] xm pause/unpause misleading error, bugzilla-daemon <=

Previous by Date:

[Xen-bugs] [Bug 239] xen hangs on a P4 3.0 ht with 4 gb of RAM, bugzilla-daemon

Next by Date:

[Xen-bugs] [Bug 240] New: Ballooning domain to 15MB crashes hard on x86_64, bugzilla-daemon

Previous by Thread:

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

Next by Thread:

[Xen-bugs] [Bug 204] too much output kills xenconsoled, bugzilla-daemon

Indexes:

[Date] [Thread] [Top] [All Lists]