[ovs-dev] [PATCH v6 1/3] ovsdb-server.7: Mention update3 as replies to monitor_cond_change.
Dumitru Ceara
dceara at redhat.com
Thu May 28 12:32:17 UTC 2020
Monitor_cond_change might trigger updates to be sent to clients as results
to condition changes. These updates can be either update2 (for monitor_cond
monitors) or update3 (for monitor_cond_since monitors). The documentation
used to mention only update2.
Signed-off-by: Dumitru Ceara <dceara at redhat.com>
Acked-by: Han Zhou <hzhou at ovn.org>
---
Documentation/ref/ovsdb-server.7.rst | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/Documentation/ref/ovsdb-server.7.rst b/Documentation/ref/ovsdb-server.7.rst
index 967761b..0441435 100644
--- a/Documentation/ref/ovsdb-server.7.rst
+++ b/Documentation/ref/ovsdb-server.7.rst
@@ -316,9 +316,9 @@ monitor request, <table-updates2> will contain any matched rows by old
condition and not matched by the new condition.
Changes according to the new conditions are automatically sent to the client
-using the ``update2`` monitor notification. An update, if any, as a result of
-a condition change, will be sent to the client before the reply to the
-``monitor_cond_change`` request.
+using the ``update2`` or ``update3`` monitor notification depending on the
+monitor method. An update, if any, as a result of a condition change, will
+be sent to the client before the reply to the ``monitor_cond_change`` request.
4.1.14 Update2 notification
---------------------------
More information about the dev
mailing list