Mark Reynolds wrote: > > On 6/12/19 11:41 AM, Rob Crittenden wrote: >> Mark Reynolds wrote: >>> http://www.port389.org/docs/389ds/design/repl-agmt-status-design.html >> conn_error is 0 in all the examples. What would this be used for? > Well there are two type of errors that can occur. One is a replication > error (missing CSN, replica busy, etc), and the other type is a > connection/LDAP failure (can not contact server, invalid credentials, no > such object, etc). This is just how its currently designed in the code, > so I carried it forward into the JSON object. Ok. What about compatibility with older versions of 389-ds, particularly tools that read replication status? Are they going to blow up with the new status format? rob _______________________________________________ 389-devel mailing list -- 389-devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to 389-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/389-devel@xxxxxxxxxxxxxxxxxxxxxxx
