[libvirt PATCH] docs: fix mistaken description of the read-only socket units

Daniel P. Berrangé berrange at redhat.com
Thu Apr 16 13:19:08 UTC 2020


Signed-off-by: Daniel P. Berrangé <berrange at redhat.com>
---
 docs/daemons.rst | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/daemons.rst b/docs/daemons.rst
index 13c244de7b..e0b95105e4 100644
--- a/docs/daemons.rst
+++ b/docs/daemons.rst
@@ -145,7 +145,7 @@ Libvirt ships a number of unit files for controlling ``libvirtd``:
   UNIX socket ``/var/run/libvirt/libvirt-sock``. This socket is recommended to
   be started on boot by default.
 
-* ``libvirtd-ro.socket`` - the unit file corresponding to the main read-write
+* ``libvirtd-ro.socket`` - the unit file corresponding to the main read-only
   UNIX socket ``/var/run/libvirt/libvirt-sock-ro``. This socket is recommended
   to be started on boot by default.
 
@@ -316,7 +316,7 @@ Libvirt ships a number of unit files for controlling ``virt${DRIVER}d``:
   recommended to be started on boot by default.
 
 * ``virt${DRIVER}d-ro.socket`` - the unit file corresponding to the main
-  read-write UNIX socket ``/var/run/libvirt/virt${DRIVER}d-sock-ro``. This
+  read-only UNIX socket ``/var/run/libvirt/virt${DRIVER}d-sock-ro``. This
   socket is recommended to be started on boot by default.
 
 * ``virt${DRIVER}d-admin.socket`` - the unit file corresponding to the
@@ -471,7 +471,7 @@ Libvirt ships a number of unit files for controlling ``virtproxyd``:
   UNIX socket ``/var/run/libvirt/libvirt-sock``. This socket is recommended to
   be started on boot by default.
 
-* ``virtproxyd-ro.socket`` - the unit file corresponding to the main read-write
+* ``virtproxyd-ro.socket`` - the unit file corresponding to the main read-only
   UNIX socket ``/var/run/libvirt/libvirt-sock-ro``. This socket is recommended
   to be started on boot by default.
 
-- 
2.25.2




More information about the libvir-list mailing list