[PATCH] Fix xm man page statement about asynchonous operation

[Michal Novotny <minovotn@redhat.com>]

[-- Attachment #1: Type: text/plain, Size: 464 bytes --]

Hi,
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.

Thanks,
Michal

Signed-off-by: Michal Novotny <minovotn@redhat.com>

-- 
Michal Novotny<minovotn@redhat.com>, RHCE
Virtualization Team (xen userspace), Red Hat


[-- Attachment #2: xen-docs-man-xm-fix-sync-statement.patch --]
[-- Type: text/x-patch, Size: 1030 bytes --]

diff -r 96917cf25bf3 docs/man/xm.pod.1
--- a/docs/man/xm.pod.1	Fri May 28 10:54:07 2010 +0100
+++ b/docs/man/xm.pod.1	Tue Jun 01 17:20:53 2010 +0200
@@ -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
 

[-- Attachment #3: Type: text/plain, Size: 138 bytes --]

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