From: Shriram Rajagopalan <rshriram@cs.ubc.ca>
To: xen-devel@lists.xen.org
Cc: ian.jackson@eu.citrix.com, ian.campbell@citrix.com
Subject: [PATCH] libxl: Remus - fix docs
Date: Sun, 27 May 2012 17:43:21 -0700 [thread overview]
Message-ID: <9ce7af13c2eae2e774ad.1338165801@athos.nss.cs.ubc.ca> (raw)
# HG changeset patch
# User Shriram Rajagopalan <rshriram@cs.ubc.ca>
# Date 1338163739 25200
# Node ID 9ce7af13c2eae2e774ad52234ff9fbb4773caee2
# Parent 53e0571f94e4bcc45270dcbd444c7c91166cef6d
libxl: Remus - fix docs
Explicitly mention that the current state of Remus support in xl
is experimental, with no disk/network buffering support.
Signed-off-by: Shriram Rajagopalan <rshriram@cs.ubc.ca>
diff -r 53e0571f94e4 -r 9ce7af13c2ea docs/man/xl.pod.1
--- a/docs/man/xl.pod.1 Fri May 25 08:21:25 2012 +0100
+++ b/docs/man/xl.pod.1 Sun May 27 17:08:59 2012 -0700
@@ -394,6 +394,9 @@
Enable Remus HA for domain. By default B<xl> relies on ssh as a transport
mechanism between the two hosts.
+N.B: Remus support in xl is still in experimental (proof-of-concept) phase.
+ There is no support for network or disk buffering at the moment.
+
B<OPTIONS>
=over 4
@@ -404,9 +407,8 @@
=item B<-b>
-Do not checkpoint the disk. Replicate memory checkpoints to /dev/null
-(blackhole). Network output buffering remains enabled (unless --no-net is
-supplied). Generally useful for debugging.
+Replicate memory checkpoints to /dev/null (blackhole).
+Generally useful for debugging.
=item B<-u>
next reply other threads:[~2012-05-28 0:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-28 0:43 Shriram Rajagopalan [this message]
2012-05-29 9:00 ` [PATCH] libxl: Remus - fix docs Ian Campbell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9ce7af13c2eae2e774ad.1338165801@athos.nss.cs.ubc.ca \
--to=rshriram@cs.ubc.ca \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).