On Thu, Mar 1, 2012 at 17:29, wrote:
> Hello,
>
> I would need a memory buffer associated per worker thread (in the worker
> MPM) or to each process (in the prefork MPM).
>
> In order to do that, I would need a map thread<->buffer. So, I would
> need a sort of thread I
ort of thread ID/key/handle that stays the same during the
lifetime of the thread and no two threads in the same process can have
the same ID/key/handle.
What is the most portable way to get this thread ID?
I thought of r->connection->id. It works but it is not very portable as
it is not guarant
thread<->buffer. So, I would
need a sort of thread ID/key/handle that stays the same during the
lifetime of the thread and no two threads in the same process can have
the same ID/key/handle.
What is the most portable way to get this thread ID?
I thought of r->connection->id. It works but it
).
In order to do that, I would need a map thread<->buffer. So, I would
need a sort of thread ID/key/handle that stays the same during the
lifetime of the thread and no two threads in the same process can have
the same ID/key/handle.
What is the most portable way to get this thread ID?
I thou
) or to each process (in the prefork MPM).
In order to do that, I would need a map thread<->buffer. So, I would
need a sort of thread ID/key/handle that stays the same during the
lifetime of the thread and no two threads in the same process can have
the same ID/key/handle.
What is the most po
thanks
-- Massimo
On 03/05/2012 08:21 PM, Rainer Jung wrote:
On 05.03.2012 11:33, Massimo Manghi wrote:
true, the ID is logged now, but is the function handling the thread id
public?
not the function, but the source. See function log_tid() in server/log.c.
Regards,
Rainer
