On 28 juin, 23:26, Tomasz Pajor ni...@puffy.pl wrote:
Hello,
Configuration is as follows.
I have a starter process which creates 3 sub processes (forks) and each
of this processes creates a number of threads.
Threads in that processes have semaphore so on KeyboardInterrupt without
sending
On 29 Giu, 07:10, OdarR olivier.da...@gmail.com wrote:
On 28 juin, 23:26, Tomasz Pajor ni...@puffy.pl wrote:
Hello,
Configuration is as follows.
I have a starter process which creates 3 sub processes (forks) and each
of this processes creates a number of threads.
Threads in that
On 29 juin, 14:44, Francesco Bochicchio bieff...@gmail.com wrote:
On 29 Giu, 07:10, OdarR olivier.da...@gmail.com wrote:
On 28 juin, 23:26, Tomasz Pajor ni...@puffy.pl wrote:
Hello,
Configuration is as follows.
I have a starter process which creates 3 sub processes (forks) and
In message cf35773f-600b-44a0-9a5b-
de39d2086...@h11g2000yqb.googlegroups.com, Francesco Bochicchio wrote:
... if the thread is waiting for a blocking I/O operation to complete,
like reading from a socket with no data or waiting for a locked resource
(i.e. semaphore) to be unlocked, it will
Hello,
Configuration is as follows.
I have a starter process which creates 3 sub processes (forks) and each
of this processes creates a number of threads.
Threads in that processes have semaphore so on KeyboardInterrupt without
sending a sigterm to the subprocess i'm not able to close
On 28 juin, 23:26, Tomasz Pajor ni...@puffy.pl wrote:
Hello,
Configuration is as follows.
I have a starter process which creates 3 sub processes (forks) and each
of this processes creates a number of threads.
Threads in that processes have semaphore so on KeyboardInterrupt without
sending
