https://fedorapeople.org/groups/389ds/ci/nightly/2019/06/13/report-389-ds-base-1.4.1.3-20190612gitb4e585f.fc30.x86_64.html
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to
On 6/12/19 12:53 PM, Rob Crittenden wrote:
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
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
Sorry Mark, my email was confusing.
First you make a good point. Giving extra info does not hurt.
I just noticed that replication status contains two RC (ldap and
replication), while init status contains three RC (ldap, replication,
connection). So the json struct should differ from
On 6/12/19 12:08 PM, thierry bordaz wrote:
Hi Mark,
Looking very good to me.
For replication status there is either ldaprc or replrc. The message
is self explaining if it is a LDAP or replication error. IMHO I think
json could only contain 'repl_status' that can contain ldaprc or replrc.
Hi Mark,
Looking very good to me.
For replication status there is either ldaprc or replrc. The message is
self explaining if it is a LDAP or replication error. IMHO I think json
could only contain 'repl_status' that can contain ldaprc or replrc.
For init status, it exists ldaprc, connrc and
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,
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?
Otherwise this looks ok to me. I assume we'll need to do coordinate
releases with IPA so the new format can be handled properly? I guess
http://www.port389.org/docs/389ds/design/repl-agmt-status-design.html
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
On 6/12/19 5:48 AM, William Brown wrote:
On 12 Jun 2019, at 11:27, thierry bordaz wrote:
On 6/12/19 9:22 AM, Ludwig Krispenz wrote:
Hi Mark,
On 06/11/2019 08:15 PM, Mark Reynolds wrote:
I am currently working on a revision of replication agreement status messages.
Previously we
> On 12 Jun 2019, at 11:27, thierry bordaz wrote:
>
>
>
> On 6/12/19 9:22 AM, Ludwig Krispenz wrote:
>> Hi Mark,
>>
>> On 06/11/2019 08:15 PM, Mark Reynolds wrote:
>>> I am currently working on a revision of replication agreement status
>>> messages. Previously we logged the status like
On 6/12/19 9:22 AM, Ludwig Krispenz wrote:
Hi Mark,
On 06/11/2019 08:15 PM, Mark Reynolds wrote:
I am currently working on a revision of replication agreement status
messages. Previously we logged the status like so:
Error (%d) - message (sub-message) ...
just to get it clear what
> On 12 Jun 2019, at 09:22, Ludwig Krispenz wrote:
>
> Hi Mark,
>
> On 06/11/2019 08:15 PM, Mark Reynolds wrote:
>> I am currently working on a revision of replication agreement status
>> messages. Previously we logged the status like so:
>>
>>Error (%d) - message (sub-message) ...
>
Hi Mark,
On 06/11/2019 08:15 PM, Mark Reynolds wrote:
I am currently working on a revision of replication agreement status
messages. Previously we logged the status like so:
Error (%d) - message (sub-message) ...
just to get it clear what you suggest, I was a bit confused about first.
14 matches
Mail list logo
