In message , 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 not service the queue and will
> not read the 'quit command' (the
On 29 juin, 14:44, Francesco Bochicchio wrote:
> On 29 Giu, 07:10, OdarR wrote:
>
>
>
> > On 28 juin, 23:26, Tomasz Pajor wrote:
>
> > > Hello,
>
> > > Configuration is as follows.
>
> > > I have a starter process which creates 3 sub processes (forks) and each
> > > of this processes creates a n
On 29 Giu, 07:10, OdarR wrote:
> On 28 juin, 23:26, Tomasz Pajor 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 28 juin, 23:26, Tomasz Pajor 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 a sigterm to t
On 28 juin, 23:26, Tomasz Pajor 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 a sigte
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 threads.
