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

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 complex, and very error prone. I'd like to allow the import task to complete before fully shutting the server down.  Code fix is trivial, but do we want the import to finish, or should the import be aborted (and database left broken)?  Thoughts?  Opinions? Thanks, Mark -- 389 Directory Server Development Team