Worker ID

[Jordan Newman]

Thanks, ngx_process_slot was what I needed.  The reason for knowing the worker # is for stat tracking, its important that the backend where the stats are being collected on knows to group them together by worker and then by server.

--
Jordan Newman

> On May 14, 2014, at 10:55 AM, Maxim Dounin <mdounin at mdounin.ru> wrote:
> 
> Hello!
> 
>> On Tue, May 13, 2014 at 09:20:07PM -0400, Jordan Newman wrote:
>> 
>> Is there a way from an nginx module to see which # worker it is? Thank you.
> 
> If you need to know worker's number, you are likely doing 
> something wrong.
> 
> Note that there may be more than one set of workers running 
> concurrently - e.g., after a configuration reload a new set of 
> workers is spawned, and only after this old workes are gracefully 
> shut down.
> 
> -- 
> Maxim Dounin
> http://nginx.org/
> 
> _______________________________________________
> nginx-devel mailing list
> nginx-devel at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx-devel