"John L. Stephens" writes:
> As the parent process terminates 'normally' (either through normal
> termination or SIGINT termination), mulitprocessing steps in and
> performs child process cleanup via the x.terminate() method. If the
> parent terminates any other way, multiprocessing doesn't have
On 3/15/2011 11:19 PM, James Mills wrote:
On Wed, Mar 16, 2011 at 12:34 PM, John L. Stephens
wrote:
I would have expected the daemonic children processes to terminate with the
parent process, regardless of how the parent process terminates, either
normally or forcefully.
As I understand it. I
On Wed, Mar 16, 2011 at 12:34 PM, John L. Stephens
wrote:
> I would have expected the daemonic children processes to terminate with the
> parent process, regardless of how the parent process terminates, either
> normally or forcefully.
As I understand it. If you forcibly kill the parent process
w
On 16/03/2011 02:34, John L. Stephens wrote:
Greetings,
I'm trying to understand the behavior of the multiprocessing.Process
daemonic attribute.
Based on what I have read, if a Process ( X ) is created, and before it
is started ( X.start() ), I should be able to set the process as
daemonic usin
Greetings,
I'm trying to understand the behavior of the multiprocessing.Process
daemonic attribute.
Based on what I have read, if a Process ( X ) is created, and before it
is started ( X.start() ), I should be able to set the process as
daemonic using X.daemon=True.
Once this attribute is
