[Xen-changelog] [xen-unstable] Fix xm man page statement about asynchonous operation

[Xen patchbot-unstable <patchbot-unstable@xxxxxxxxxxxxxxxxxxx>]

# HG changeset patch
# User Keir Fraser <keir.fraser@xxxxxxxxxx>
# Date 1275472175 -3600
# Node ID 331b0a934a2033fa830915e080bbca9d8adf19b6
# Parent  ab4281135770d136cfc2deb1ff0bf8a6b898abc6
Fix xm man page statement about asynchonous operation

The man page for xm command states that many commands acts
asynchronously which is not true. According to my experience most
commands does act synchronously with several exceptions, like create,
shutdown, mem-set and vcpu-set commands so this fixes the paragraph
available in this xm man page.

Signed-off-by: Michal Novotny <minovotn@xxxxxxxxxx>
---
 docs/man/xm.pod.1 |   10 ++++------
 1 files changed, 4 insertions(+), 6 deletions(-)

diff -r ab4281135770 -r 331b0a934a20 docs/man/xm.pod.1
--- a/docs/man/xm.pod.1 Wed Jun 02 10:38:55 2010 +0100
+++ b/docs/man/xm.pod.1 Wed Jun 02 10:49:35 2010 +0100
@@ -40,12 +40,10 @@ communications channels used to talk to 
 communications channels used to talk to the hypervisor.  Running as
 non root will return an error.
 
-Most B<xm> commands act asynchronously, so just because the B<xm>
-command returned doesn't mean the action is complete.  This is
-important, as many operations on domains, like create and shutdown,
-can take considerable time (30 seconds or more) to bring the machine
-into a fully compliant state.  If you want to know when one of these
-actions has finished you must poll through B<xm list> periodically.
+Most B<xm> commands act synchronously, except maybe create, shutdown,
+mem-set and vcpu-set. The fact that the B<xm> command returned doesn't
+necessarily mean that the action is complete and you must poll through
+xm list periodically to detect that the operation completed.
 
 =head1 DOMAIN SUBCOMMANDS
 

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