[389-devel] Re: Logging future direction and ideas.

2019-05-22 Thread William Brown
> On 22 May 2019, at 22:36, Ludwig Krispenz wrote: > > > On 05/17/2019 12:44 AM, William Brown wrote: > > I think this would be a "final goal", so to formalise the stages: > > * Add build tooling and a simple (dummy) log thread as a "getting started". > Supplement with documentation on

[389-devel] Re: Logging future direction and ideas.

2019-05-22 Thread Ludwig Krispenz
On 05/17/2019 12:44 AM, William Brown wrote: I think this would be a "final goal", so to formalise the stages: * Add build tooling and a simple (dummy) log thread as a "getting started". Supplement with documentation on wiki. * Fill-in the log thread to support an "operation log", and add

[389-devel] Re: Logging future direction and ideas.

2019-05-16 Thread William Brown
> On 17 May 2019, at 00:16, Ludwig Krispenz wrote: > > > On 05/16/2019 02:56 AM, William Brown wrote: >> Replying to both Simon and Ludwig in the one mail ... >> >> To just comment to one point from Ludwig: >> >>> This may sound too negative, I agree that logging deserves attention and >>>

[389-devel] Re: Logging future direction and ideas.

2019-05-16 Thread Ludwig Krispenz
On 05/16/2019 02:56 AM, William Brown wrote: Replying to both Simon and Ludwig in the one mail ... To just comment to one point from Ludwig: This may sound too negative, I agree that logging deserves attention and improvement, but we need to agree on what we want to achieve. I don't think

[389-devel] Re: Logging future direction and ideas.

2019-05-15 Thread William Brown
Replying to both Simon and Ludwig in the one mail ... To just comment to one point from Ludwig: > This may sound too negative, I agree that logging deserves attention and > improvement, but we need to agree on what we want to achieve. I don't think this is negative, at all and I think it's

[389-devel] Re: Logging future direction and ideas.

2019-05-15 Thread Ludwig
Hi William, this is a good starting point to discuss and decide how to move forward with logging (although it looks like you are already some steps ahead). I have no strong ties to existing logging format and if we do it in rust or not I don't care, but I do not want to use existing

[389-devel] Re: Logging future direction and ideas.

2019-05-12 Thread William Brown
> On 10 May 2019, at 23:59, Rich Megginson wrote: > > On 5/9/19 9:13 PM, William Brown wrote: >> Hi all, >> >> So I think it's time for me to write some logging code to improve the >> situation. Relevant links before we start: >> >> https://pagure.io/389-ds-base/issue/49415 >>

[389-devel] Re: Logging future direction and ideas.

2019-05-10 Thread Rich Megginson
On 5/9/19 9:13 PM, William Brown wrote: Hi all, So I think it's time for me to write some logging code to improve the situation. Relevant links before we start: https://pagure.io/389-ds-base/issue/49415 http://www.port389.org/docs/389ds/design/logging-performance-improvement.html