[bind10-dev] exit from multiple threads python process

[Likun Zhang]

Vorner

> I'm not sure. The main thread listed the threads by threading.enumerate(),
> which means all threads in current process. Now imagine a library (some, not
> even
> ours) creates a cleanup/watchdog/whatever thread. It doesn't have it's own way
> to terminate, but is set as a daemon thread. And we explicitly .join() it.
> Another possibility would be ‒ I'm not sure if threading.enumerate() could
> include pthreads created from underlaying C/C++ code ‒ I could imagine it might.
> Now, if a datasource (for example) has a thread…
> 
> I'm not directly opposed to having the bit of code, if you think it is worth to know
> when everything terminated, but it just doesn't seem right to me.
> 

Yeah, vorner, I agree with you totally from technical (programmer) perspective, since each programmer want to keep bugs away. 

But now, let's see the problem from *user's* perpective, we'd better not frustrate our users, as shane suggested : 

"This may not seem like much, but as an administrator BIND 9 has been very frustrating in use because you don't know when it has started or not, so I can imagine actually knowing when a process is done could be quite nice. :)"

So my suggestion is : let's keep the old way xfrout did, and fix the bug(If we have it in the future) for the deamon thread which doesn't have it's own way to terminate.

Thanks
Likun