It seems best to be explicit about this. Signed-off-by: Ben Pfaff <[email protected]> --- ovsdb/ovsdb-server.1.in | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/ovsdb/ovsdb-server.1.in b/ovsdb/ovsdb-server.1.in index cf3884ccc294..f1c6466ccb75 100644 --- a/ovsdb/ovsdb-server.1.in +++ b/ovsdb/ovsdb-server.1.in @@ -512,7 +512,8 @@ is the requested value for this session. This value is valid only after "monitor_cond_change" is committed. A user can use these values to distinguish between update messages before conditions update and after. The <monitor-cond-update-requests> object maps the name of the table to an array of -<monitor-cond-update-request>. +<monitor-cond-update-request>. Monitored tables not included in +<monitor-cond-update-requests> retain their current conditions. . .IP Each <monitor-cond-update-request> is an object with the following members: -- 2.10.2 _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
