[389-devel] Re: Implementing Referential Integrity by using a queue instead of a file

2017-07-10 Thread Ludwig
On 07/10/2017 12:13 AM, William Brown wrote: On Fri, 2017-07-07 at 11:44 +0200, Ludwig Krispenz wrote: On 07/07/2017 10:44 AM, Ludwig Krispenz wrote: On 07/07/2017 07:10 AM, William Brown wrote: Any thoughts or objections on the above would be welcome. The only problem with going to a

[389-devel] Re: Implementing Referential Integrity by using a queue instead of a file

2017-07-09 Thread William Brown
On Fri, 2017-07-07 at 11:44 +0200, Ludwig Krispenz wrote: > On 07/07/2017 10:44 AM, Ludwig Krispenz wrote: > > > > On 07/07/2017 07:10 AM, William Brown wrote: > >> Any thoughts or objections on the above would be welcome. > > The only problem with going to a queue is if the server goes

[389-devel] Re: Implementing Referential Integrity by using a queue instead of a file

2017-07-07 Thread Ludwig Krispenz
On 07/07/2017 03:17 PM, Mark Reynolds wrote: On 07/07/2017 04:44 AM, Ludwig Krispenz wrote: On 07/07/2017 07:10 AM, William Brown wrote: Any thoughts or objections on the above would be welcome. The only problem with going to a queue is if the server goes down unexpectedly. In such a

[389-devel] Re: Implementing Referential Integrity by using a queue instead of a file

2017-07-07 Thread Mark Reynolds
On 07/07/2017 04:44 AM, Ludwig Krispenz wrote: > > On 07/07/2017 07:10 AM, William Brown wrote: >> Any thoughts or objections on the above would be welcome. > The only problem with going to a queue is if the server goes down > unexpectedly. In such a case those RI updates would be

[389-devel] Re: Implementing Referential Integrity by using a queue instead of a file

2017-07-07 Thread Ludwig Krispenz
On 07/07/2017 10:44 AM, Ludwig Krispenz wrote: On 07/07/2017 07:10 AM, William Brown wrote: Any thoughts or objections on the above would be welcome. The only problem with going to a queue is if the server goes down unexpectedly. In such a case those RI updates would be lost. We already

[389-devel] Re: Implementing Referential Integrity by using a queue instead of a file

2017-07-07 Thread Ludwig Krispenz
On 07/07/2017 07:10 AM, William Brown wrote: Any thoughts or objections on the above would be welcome. The only problem with going to a queue is if the server goes down unexpectedly. In such a case those RI updates would be lost. We already have this issue because there is a delay between

[389-devel] Re: Implementing Referential Integrity by using a queue instead of a file

2017-07-06 Thread William Brown
> >>> > >>> Any thoughts or objections on the above would be welcome. > >> The only problem with going to a queue is if the server goes down > >> unexpectedly. In such a case those RI updates would be lost. > > We already have this issue because there is a delay between the change > > to the

[389-devel] Re: Implementing Referential Integrity by using a queue instead of a file

2017-07-06 Thread Mark Reynolds
On 07/06/2017 08:13 PM, William Brown wrote: > On Thu, 2017-07-06 at 14:33 -0400, Mark Reynolds wrote: >> On 07/06/2017 01:07 PM, Ilias Stamatis wrote: >>> Hello, >>> >>> A desire had been expressed to get rid of referint plugin's logfile: >>> https://pagure.io/389-ds-base/issue/49202 >>> >>> It

[389-devel] Re: Implementing Referential Integrity by using a queue instead of a file

2017-07-06 Thread William Brown
On Thu, 2017-07-06 at 14:33 -0400, Mark Reynolds wrote: > > On 07/06/2017 01:07 PM, Ilias Stamatis wrote: > > Hello, > > > > A desire had been expressed to get rid of referint plugin's logfile: > > https://pagure.io/389-ds-base/issue/49202 > > > > It finally turns out that this file is used for

[389-devel] Re: Implementing Referential Integrity by using a queue instead of a file

2017-07-06 Thread Mark Reynolds
On 07/06/2017 01:07 PM, Ilias Stamatis wrote: > Hello, > > A desire had been expressed to get rid of referint plugin's logfile: > https://pagure.io/389-ds-base/issue/49202 > > It finally turns out that this file is used for other purposes than > real logging. > > The referint plugin currently