* docs/libvir.html docs/uri.html: remove references to libvirt_qemud

  and replace them with libvirtd
Daniel

diff --git a/ChangeLog b/ChangeLog
index 93dd8d8fefed55d4884dad80b59924d1e0ad0212..15cd5e950962c22965c8e81623e6b2cd674f6b48 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,8 @@
+Wed Sep  5 16:31:00 CEST 2007 Daniel Veillard <veillard@redhat.com>
+
+       * docs/libvir.html docs/uri.html: remove references to libvirt_qemud
+         and replace them with libvirtd
+
 Mon Sep  3 18:29:05 CEST 2007 Daniel Veillard <veillard@redhat.com>
 
        * src/openvz_conf.c src/openvz_conf.h src/openvz_driver.c: a bit

diff --git a/docs/libvir.html b/docs/libvir.html
index dcede5519d89a1ac0551d0b98ebc85ae46c67a77..94567c66bb0ec8fb7ca3409c3f5ea190f94abe32 100644 (file)
--- a/docs/libvir.html
+++ b/docs/libvir.html
@@ -2478,18 +2478,19 @@ use the URI <code>xen:///</code>.
 
 <p>
 To use QEMU support in libvirt you must be running the
-<code>libvirt_qemud</code> daemon.  The purpose of this
+<code>libvirtd</code> daemon (named <code>libvirt_qemud</code>
+in releases prior to 0.3.0).  The purpose of this
 daemon is to manage qemu instances.
 </p>
 
 <p>
-The <code>libvirt_qemud</code> daemon can be run in two ways.  It may
+The <code>libvirtd</code> daemon can be run in two ways.  It may
 be started by init scripts when the machine boots and run in "system
-mode" (<code>libvirt_qemud --system</code>), in which case it manages
+mode" (<code>libvirtd --system</code>), in which case it manages
 qemu instances on behalf of all users of the machine.  It may be also
 be started by the local user in what is known as "session mode"
-(<code>libvirt_qemud --session</code>), to manage qemu instances for
-just the current user.  If no <code>libvirt_qemud</code> is running at
+(<code>libvirtd --session</code>), to manage qemu instances for
+just the current user.  If no <code>libvirtd</code> is running at
 all, then the qemu driver starts one running in session mode.
 </p>
 
@@ -2503,7 +2504,7 @@ So to connect to the daemon, one of two different URIs is used:
 </ul>
 
 <p>
-(If you do <code>libvirt_qemud --help</code>, the daemon will print
+(If you do <code>libvirtd --help</code>, the daemon will print
 out the paths of the Unix domain socket(s) that it listens on in
 the various different modes).
 </p>

diff --git a/docs/uri.html b/docs/uri.html
index be365751ae438726fb64a1f87807c2e6ffd0db27..9b4b23bb1c57ca2027a25f8652012c10f185bf78 100644 (file)
--- a/docs/uri.html
+++ b/docs/uri.html
@@ -47,23 +47,24 @@ To access a Xen hypervisor running on the local machine
 use the URI <code>xen:///</code>.
 </p><h3><a name="URI_qemu" id="URI_qemu">qemu:///... QEMU and KVM URIs</a></h3><p>
 To use QEMU support in libvirt you must be running the
-<code>libvirt_qemud</code> daemon.  The purpose of this
+<code>libvirtd</code> daemon (named <code>libvirt_qemud</code>
+in releases prior to 0.3.0).  The purpose of this
 daemon is to manage qemu instances.
 </p><p>
-The <code>libvirt_qemud</code> daemon can be run in two ways.  It may
+The <code>libvirtd</code> daemon can be run in two ways.  It may
 be started by init scripts when the machine boots and run in "system
-mode" (<code>libvirt_qemud --system</code>), in which case it manages
+mode" (<code>libvirtd --system</code>), in which case it manages
 qemu instances on behalf of all users of the machine.  It may be also
 be started by the local user in what is known as "session mode"
-(<code>libvirt_qemud --session</code>), to manage qemu instances for
-just the current user.  If no <code>libvirt_qemud</code> is running at
+(<code>libvirtd --session</code>), to manage qemu instances for
+just the current user.  If no <code>libvirtd</code> is running at
 all, then the qemu driver starts one running in session mode.
 </p><p>
 So to connect to the daemon, one of two different URIs is used:
 </p><ul><li> <code>qemu:///system</code> connects to a system mode daemon. </li>
 <li> <code>qemu:///session</code> connects to a session mode daemon. </li>
 </ul><p>
-(If you do <code>libvirt_qemud --help</code>, the daemon will print
+(If you do <code>libvirtd --help</code>, the daemon will print
 out the paths of the Unix domain socket(s) that it listens on in
 the various different modes).
 </p><p>