summaryrefslogtreecommitdiff
path: root/Documentation/ref
diff options
context:
space:
mode:
authorDumitru Ceara <dceara@redhat.com>2020-05-28 14:32:17 +0200
committerIlya Maximets <i.maximets@ovn.org>2020-06-15 01:04:10 +0200
commitf05d17e2789c30ad38bd3c502cdbe4719f9832fe (patch)
tree075fe82368580236bf9df849b7e810d66a486f19 /Documentation/ref
parent5042815d8fe58e19b58e77d4d87b59951f6fdeb8 (diff)
downloadopenvswitch-f05d17e2789c30ad38bd3c502cdbe4719f9832fe.tar.gz
ovsdb-server.7: Mention update3 as replies to monitor_cond_change.
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@redhat.com> Acked-by: Han Zhou <hzhou@ovn.org> Signed-off-by: Ilya Maximets <i.maximets@ovn.org>
Diffstat (limited to 'Documentation/ref')
-rw-r--r--Documentation/ref/ovsdb-server.7.rst6
1 files changed, 3 insertions, 3 deletions
diff --git a/Documentation/ref/ovsdb-server.7.rst b/Documentation/ref/ovsdb-server.7.rst
index 967761bdf..04414350a 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
---------------------------