[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] 389 DS nightly 2019-10-15 - 96% PASS

2019-10-14 Thread vashirov
https://fedorapeople.org/groups/389ds/ci/nightly/2019/10/15/report-389-ds-base-1.4.2.2-20191014gitc95f6cf.fc30.x86_64.html ___ 389-devel mailing list -- 389-devel@lists.fedoraproject.org To unsubscribe send an email to

[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] Discuss/Review: tls tools for dsctl

2019-10-14 Thread William Brown
Hi, https://pagure.io/389-ds-base/pull-request/50648 https://pagure.io/389-ds-base/issue/50007 I'd like some feedback on this - especially look at Mark and Simon here - about how we should "display" certificates in the list/show commands. What data should we show? Right now it's the

[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 >

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

2019-10-14 Thread Mark Reynolds
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 at a later time.  Unfortunately the code that handles this is

[389-devel] please review: PR 50630 - very slow import with heavily nested tree

2019-10-14 Thread Mark Reynolds
https://pagure.io/389-ds-base/pull-request/50630 -- 389 Directory Server Development Team ___ 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: