Lua Variable access bug?
Sirsiwal, Umesh
usirsiwal at verivue.com
Thu May 17 13:36:48 UTC 2012
On my end the agentzh's patch is working correctly.
-Umesh
On 05/17/2012 09:13 AM, agentzh wrote:
> On Thu, May 17, 2012 at 9:06 PM, Maxim Dounin<mdounin at mdounin.ru> wrote:
>> No, disregard this patch. It will break things if new
>> configuration will be rejected for some reason, as global in
>> master will be left in an inconsistent state. As a result
>> incorrect worker processes will be spawn e.g. after abnormal
>> termination of a worker process (or after SIGWINCH + SIGHUP
>> sequence).
>>
>> Allocating temporary copy of a variable looks like the only
>> correct way.
>>
> Indeed. Modifying static/global variables is almost always dangerous
> for configuration reloading :)
>
> Thanks!
> -agentzh
>
> _______________________________________________
> nginx-devel mailing list
> nginx-devel at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx-devel
More information about the nginx-devel
mailing list