[389-devel] Re: Should stopping the server interrupt an import job?

2019-10-16 Thread William Brown
> On 16 Oct 2019, at 00:27, Mark Reynolds wrote: > > > On 10/14/19 11:13 PM, William Brown wrote: >> >>> On 15 Oct 2019, at 15:51, Mark Reynolds wrote: >>> >>> >>> On 10/14/19 6:35 PM, William Brown wrote: > On 15 Oct 2019, at 06:58, Mark Reynolds wrote: > > So we are

[389-devel] Re: Should stopping the server interrupt an import job?

2019-10-15 Thread Mark Reynolds
On 10/14/19 11:13 PM, William Brown wrote: On 15 Oct 2019, at 15:51, Mark Reynolds wrote: On 10/14/19 6:35 PM, William Brown wrote: On 15 Oct 2019, at 06:58, Mark Reynolds wrote: So we are finding these race conditions (leading to heap-use-after-free) when you stop the server while an

[389-devel] Re: Should stopping the server interrupt an import job?

2019-10-14 Thread William Brown
> On 15 Oct 2019, at 15:51, Mark Reynolds wrote: > > > On 10/14/19 6:35 PM, William Brown wrote: >> >>> On 15 Oct 2019, at 06:58, Mark Reynolds wrote: >>> >>> So we are finding these race conditions (leading to heap-use-after-free) >>> when you stop the server while an import task is

[389-devel] Re: Should stopping the server interrupt an import job?

2019-10-14 Thread Mark Reynolds
On 10/14/19 6:35 PM, William Brown wrote: On 15 Oct 2019, at 06:58, Mark Reynolds wrote: So we are finding these race conditions (leading to heap-use-after-free) when you stop the server while an import task is running. The current code aborts the task which leaves the database unusable

[389-devel] Re: Should stopping the server interrupt an import job?

2019-10-14 Thread William Brown
> On 15 Oct 2019, at 06:58, Mark Reynolds wrote: > > So we are finding these race conditions (leading to heap-use-after-free) when > you stop the server while an import task is running. The current code aborts > the task which leaves the database unusable until it is fully reinitialized >