Maxim, but is it possible somehow to implement to handle SIGHUP the same way as exit_process?
On Tue, Oct 28, 2014 at 5:17 PM, <nginx-devel-requ...@nginx.org> wrote: > Send nginx-devel mailing list submissions to > nginx-devel@nginx.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://mailman.nginx.org/mailman/listinfo/nginx-devel > or, via email, send a message with subject or body 'help' to > nginx-devel-requ...@nginx.org > > You can reach the person managing the list at > nginx-devel-ow...@nginx.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of nginx-devel digest..." > > > Today's Topics: > > 1. [nginx] Upstream: limited next_upstream time and tries when > reso... (Roman Arutyunyan) > 2. Re: SIGHUP and ngx_module_t (Maxim Dounin) > 3. Re: [PATCH] Upstream: limited next_upstream time and tries > when resolving DNS (Roman Arutyunyan) > 4. Re: [PATCH] Support cross compiling with MinGW-w64 on Debian > GNU/Linux (Kouhei Sutou) > 5. [nginx] Win32: made build-able with MinGW-w64 gcc. (Maxim Dounin) > 6. Re: [PATCH] Support cross compiling with MinGW-w64 on Debian > GNU/Linux (Maxim Dounin) > 7. Re: [PATCH] SPDY: stop emitting empty header values > (Valentin V. Bartenev) > 8. Re: [PATCH] Support cross compiling with MinGW-w64 on Debian > GNU/Linux (Kouhei Sutou) > 9. [PATCH] Add Win32 related files into tar.gz (Kouhei Sutou) > 10. [nginx] Updated OpenSSL used for win32 builds. (Maxim Dounin) > 11. [nginx] nginx-1.7.7-RELEASE (Maxim Dounin) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 28 Oct 2014 12:48:14 +0000 > From: Roman Arutyunyan <a...@nginx.com> > To: nginx-devel@nginx.org > Subject: [nginx] Upstream: limited next_upstream time and tries when > reso... > Message-ID: > <hg.5a042519bfe7.1414500494.6026610855610030...@dev.nginx.com> > Content-Type: text/plain; charset="us-ascii" > > details: http://hg.nginx.org/nginx/rev/5a042519bfe7 > branches: > changeset: 5885:5a042519bfe7 > user: Gu Feng <flygo...@126.com> > date: Mon Oct 27 19:52:03 2014 +0800 > description: > Upstream: limited next_upstream time and tries when resolving DNS. > > When got multiple upstream IP addresses using DNS resolving, the number of > upstreams tries and the maxinum time spent for these tries were not > affected. > This patch fixed it. > > diffstat: > > src/http/ngx_http_upstream.c | 8 ++++++++ > 1 files changed, 8 insertions(+), 0 deletions(-) > > diffs (18 lines): > > diff -r 8486205d10db -r 5a042519bfe7 src/http/ngx_http_upstream.c > --- a/src/http/ngx_http_upstream.c Tue Oct 28 12:29:59 2014 +0300 > +++ b/src/http/ngx_http_upstream.c Mon Oct 27 19:52:03 2014 +0800 > @@ -981,6 +981,14 @@ ngx_http_upstream_resolve_handler(ngx_re > ngx_resolve_name_done(ctx); > ur->ctx = NULL; > > + u->peer.start_time = ngx_current_msec; > + > + if (u->conf->next_upstream_tries > + && u->peer.tries > u->conf->next_upstream_tries) > + { > + u->peer.tries = u->conf->next_upstream_tries; > + } > + > ngx_http_upstream_connect(r, u); > > failed: > > > > ------------------------------ > > Message: 2 > Date: Tue, 28 Oct 2014 15:51:19 +0300 > From: Maxim Dounin <mdou...@mdounin.ru> > To: nginx-devel@nginx.org > Subject: Re: SIGHUP and ngx_module_t > Message-ID: <20141028125119.gk45...@mdounin.ru> > Content-Type: text/plain; charset=us-ascii > > Hello! > > On Tue, Oct 28, 2014 at 08:30:15AM +0200, Donatas Abraitis wrote: > > > Hello, > > > > is it true, that SIGHUP is not handled by ngx_module_t /* exit process > */ ? > > > > I mean if I have these defined: > > > > ngx_http_modsecurity_terminate, /* exit process */ > > ngx_http_modsecurity_terminate, /* exit master */ > > > > So, sending SIGHUP to the master it doesn't call the > > ngx_http_modsecurity_terminate(). If sending SIGTERM it does. How is it > for > > real? > > The exit_process callback is called on process exit, not on > SIGHUP. There is a difference, see here: > > http://nginx.org/en/docs/control.html > > -- > Maxim Dounin > http://nginx.org/ > > > > ------------------------------ > > Message: 3 > Date: Tue, 28 Oct 2014 15:52:38 +0300 > From: Roman Arutyunyan <a...@nginx.com> > To: nginx-devel@nginx.org > Subject: Re: [PATCH] Upstream: limited next_upstream time and tries > when resolving DNS > Message-ID: <b45b7d29-3f17-4086-8319-d33c24f57...@nginx.com> > Content-Type: text/plain; charset=us-ascii > > > On 27 Oct 2014, at 14:53, Gu Feng <flygo...@126.com> wrote: > > > # HG changeset patch > > # User Gu Feng <flygo...@126.com> > > # Date 1414410723 -28800 > > # Mon Oct 27 19:52:03 2014 +0800 > > # Node ID ccc3b86835da54273c333e7d6a00f68e0b0e6c27 > > # Parent 973fded4f461f3a397779b3a1dc80881b1b34974 > > Upstream: limited next_upstream time and tries when resolving DNS. > > > > When got multiple upstream IP addresses using DNS resolving, the number > of > > upstreams tries and the maxinum time spent for these tries were not > affected. > > This patch fixed it. > > > > diff -r 973fded4f461 -r ccc3b86835da src/http/ngx_http_upstream.c > > --- a/src/http/ngx_http_upstream.c Wed Oct 15 22:57:23 2014 +0400 > > +++ b/src/http/ngx_http_upstream.c Mon Oct 27 19:52:03 2014 +0800 > > @@ -974,6 +974,14 @@ ngx_http_upstream_resolve_handler(ngx_re > > ngx_resolve_name_done(ctx); > > ur->ctx = NULL; > > > > + u->peer.start_time = ngx_current_msec; > > + > > + if (u->conf->next_upstream_tries > > + && u->peer.tries > u->conf->next_upstream_tries) > > + { > > + u->peer.tries = u->conf->next_upstream_tries; > > + } > > + > > ngx_http_upstream_connect(r, u); > > > > failed: > > > > _______________________________________________ > > nginx-devel mailing list > > nginx-devel@nginx.org > > http://mailman.nginx.org/mailman/listinfo/nginx-devel > > > > Thanks, committed. > > > ------------------------------ > > Message: 4 > Date: Tue, 28 Oct 2014 22:04:00 +0900 (JST) > From: Kouhei Sutou <k...@cozmixng.org> > To: nginx-devel@nginx.org > Subject: Re: [PATCH] Support cross compiling with MinGW-w64 on Debian > GNU/Linux > Message-ID: <20141028.220400.1975564655674477555....@cozmixng.org> > Content-Type: Text/Plain; charset=us-ascii > > Hi, > > In <20141027174711.gd45...@mdounin.ru> > "Re: [PATCH] Support cross compiling with MinGW-w64 on Debian GNU/Linux" > on Mon, 27 Oct 2014 20:47:11 +0300, > Maxim Dounin <mdou...@mdounin.ru> wrote: > > > - the NGX_GNUC_64 macro was removed, __MINGW64_VERSION_MAJOR > > tested directly instead; > > > > - the #include <_mingw.h> removed as tests are after includes now, > > see [1]; > > > > - some style nits. > > > > Please test if it still works for you. > > Thanks for providing your patch. > > I confirmed that it works well with both > x86_64-w64-mingw32-gcc and i686-w64-mingw32-gcc! > > > Please push the patch. > > > Thanks, > -- > kou > > > > ------------------------------ > > Message: 5 > Date: Tue, 28 Oct 2014 13:31:26 +0000 > From: Maxim Dounin <mdou...@mdounin.ru> > To: nginx-devel@nginx.org > Subject: [nginx] Win32: made build-able with MinGW-w64 gcc. > Message-ID: > <hg.5d4e4619982f.1414503086.6026610855610030...@dev.nginx.com> > Content-Type: text/plain; charset="us-ascii" > > details: http://hg.nginx.org/nginx/rev/5d4e4619982f > branches: > changeset: 5886:5d4e4619982f > user: Kouhei Sutou <k...@cozmixng.org> > date: Wed Oct 15 21:15:01 2014 +0900 > description: > Win32: made build-able with MinGW-w64 gcc. > > diffstat: > > src/os/win32/ngx_win32_config.h | 37 > +++++++++++++++++++++++++++++++++++-- > 1 files changed, 35 insertions(+), 2 deletions(-) > > diffs (88 lines): > > diff --git a/src/os/win32/ngx_win32_config.h > b/src/os/win32/ngx_win32_config.h > --- a/src/os/win32/ngx_win32_config.h > +++ b/src/os/win32/ngx_win32_config.h > @@ -37,14 +37,24 @@ > #include <shellapi.h> > #include <stddef.h> /* offsetof() */ > > -#ifdef __GNUC__ > +#ifdef __MINGW64_VERSION_MAJOR > + > +/* GCC MinGW-w64 supports _FILE_OFFSET_BITS */ > +#define _FILE_OFFSET_BITS 64 > + > +#elif defined __GNUC__ > + > /* GCC MinGW's stdio.h includes sys/types.h */ > #define _OFF_T_ > + > #endif > > #include <stdio.h> > #include <stdlib.h> > #include <stdarg.h> > +#ifdef __MINGW64_VERSION_MAJOR > +#include <stdint.h> > +#endif > #include <ctype.h> > #include <locale.h> > > @@ -136,16 +146,21 @@ typedef unsigned short int uint16_t; > typedef __int64 int64_t; > typedef unsigned __int64 uint64_t; > > -#ifndef __WATCOMC__ > +#if !defined(__WATCOMC__) && !defined(__MINGW64_VERSION_MAJOR) > typedef int intptr_t; > typedef u_int uintptr_t; > #endif > > > +#ifndef __MINGW64_VERSION_MAJOR > + > /* Windows defines off_t as long, which is 32-bit */ > typedef __int64 off_t; > #define _OFF_T_DEFINED > > +#endif > + > + > #ifdef __WATCOMC__ > > /* off_t is redefined by sys/types.h used by zlib.h */ > @@ -164,17 +179,35 @@ typedef unsigned int ino_t; > #endif > > > +#ifndef __MINGW64_VERSION_MAJOR > typedef int ssize_t; > +#endif > + > + > typedef uint32_t in_addr_t; > typedef u_short in_port_t; > typedef int sig_atomic_t; > > > +#ifdef _WIN64 > + > +#define NGX_PTR_SIZE 8 > +#define NGX_SIZE_T_LEN (sizeof("-9223372036854775808") - 1) > +#define NGX_MAX_SIZE_T_VALUE 9223372036854775807 > +#define NGX_TIME_T_LEN (sizeof("-9223372036854775808") - 1) > +#define NGX_TIME_T_SIZE 8 > + > +#else > + > #define NGX_PTR_SIZE 4 > #define NGX_SIZE_T_LEN (sizeof("-2147483648") - 1) > #define NGX_MAX_SIZE_T_VALUE 2147483647 > #define NGX_TIME_T_LEN (sizeof("-2147483648") - 1) > #define NGX_TIME_T_SIZE 4 > + > +#endif > + > + > #define NGX_OFF_T_LEN (sizeof("-9223372036854775807") - 1) > #define NGX_MAX_OFF_T_VALUE 9223372036854775807 > #define NGX_SIG_ATOMIC_T_SIZE 4 > > > > ------------------------------ > > Message: 6 > Date: Tue, 28 Oct 2014 16:38:02 +0300 > From: Maxim Dounin <mdou...@mdounin.ru> > To: nginx-devel@nginx.org > Subject: Re: [PATCH] Support cross compiling with MinGW-w64 on Debian > GNU/Linux > Message-ID: <20141028133802.gl45...@mdounin.ru> > Content-Type: text/plain; charset=us-ascii > > Hello! > > On Tue, Oct 28, 2014 at 10:04:00PM +0900, Kouhei Sutou wrote: > > > Hi, > > > > In <20141027174711.gd45...@mdounin.ru> > > "Re: [PATCH] Support cross compiling with MinGW-w64 on Debian > GNU/Linux" on Mon, 27 Oct 2014 20:47:11 +0300, > > Maxim Dounin <mdou...@mdounin.ru> wrote: > > > > > - the NGX_GNUC_64 macro was removed, __MINGW64_VERSION_MAJOR > > > tested directly instead; > > > > > > - the #include <_mingw.h> removed as tests are after includes now, > > > see [1]; > > > > > > - some style nits. > > > > > > Please test if it still works for you. > > > > Thanks for providing your patch. > > > > I confirmed that it works well with both > > x86_64-w64-mingw32-gcc and i686-w64-mingw32-gcc! > > > > > > Please push the patch. > > Committed, thanks. > > -- > Maxim Dounin > http://nginx.org/ > > > > ------------------------------ > > Message: 7 > Date: Tue, 28 Oct 2014 16:39:06 +0300 > From: "Valentin V. Bartenev" <vb...@nginx.com> > To: nginx-devel@nginx.org > Cc: Maxim Dounin <mdou...@mdounin.ru> > Subject: Re: [PATCH] SPDY: stop emitting empty header values > Message-ID: <6234114.T01q3fE4Uv@vbart-workstation> > Content-Type: text/plain; charset="us-ascii" > > On Monday 27 October 2014 14:33:15 Piotr Sikora wrote: > > # HG changeset patch > > # User Piotr Sikora <pi...@cloudflare.com> > > # Date 1414445156 25200 > > # Mon Oct 27 14:25:56 2014 -0700 > > # Node ID e590d484a7f9d2750e2cd45ea16c601ae01cb607 > > # Parent ee9230cd4bda9f9e7e83f7baf37d66ad6bb9b0c1 > > SPDY: stop emitting empty header values. > > > > Previously, nginx would emit empty values in a header with multiple, > > NULL-separated values. > > > > This is forbidden by the SPDY specification, which requires headers to > > have either a single (possibly empty) value or multiple, NULL-separated > > non-empty values. > > > > Signed-off-by: Piotr Sikora <pi...@cloudflare.com> > > > > diff -r ee9230cd4bda -r e590d484a7f9 > src/http/ngx_http_spdy_filter_module.c > > --- a/src/http/ngx_http_spdy_filter_module.c Mon Oct 27 21:14:12 2014 > +0300 > > +++ b/src/http/ngx_http_spdy_filter_module.c Mon Oct 27 14:25:56 2014 > -0700 > > @@ -493,9 +493,13 @@ ngx_http_spdy_header_filter(ngx_http_req > > continue; > > } > > > > - *last++ = '\0'; > > + if (h[j].value.len) { > > + if (last != p) { > > + *last++ = '\0'; > > + } > > > > - last = ngx_cpymem(last, h[j].value.data, h[j].value.len); > > + last = ngx_cpymem(last, h[j].value.data, > h[j].value.len); > > + } > > > > h[j].hash = 2; > > } > > > > > Ok. Ruslan? Maxim? Will you approve the patch for commit? > > wbr, Valentin V. Bartenev > > > > ------------------------------ > > Message: 8 > Date: Tue, 28 Oct 2014 22:44:26 +0900 (JST) > From: Kouhei Sutou <k...@cozmixng.org> > To: nginx-devel@nginx.org > Subject: Re: [PATCH] Support cross compiling with MinGW-w64 on Debian > GNU/Linux > Message-ID: <20141028.224426.1385733153224259244....@cozmixng.org> > Content-Type: Text/Plain; charset=us-ascii > > Hi, > > In <20141028133802.gl45...@mdounin.ru> > "Re: [PATCH] Support cross compiling with MinGW-w64 on Debian GNU/Linux" > on Tue, 28 Oct 2014 16:38:02 +0300, > Maxim Dounin <mdou...@mdounin.ru> wrote: > > >> > - the NGX_GNUC_64 macro was removed, __MINGW64_VERSION_MAJOR > >> > tested directly instead; > >> > > >> > - the #include <_mingw.h> removed as tests are after includes now, > >> > see [1]; > >> > > >> > - some style nits. > >> > > >> > Please test if it still works for you. > >> > >> Thanks for providing your patch. > >> > >> I confirmed that it works well with both > >> x86_64-w64-mingw32-gcc and i686-w64-mingw32-gcc! > >> > >> > >> Please push the patch. > > > > Committed, thanks. > > Thanks!!! > > -- > kou > > > > ------------------------------ > > Message: 9 > Date: Tue, 28 Oct 2014 23:19:17 +0900 (JST) > From: Kouhei Sutou <k...@cozmixng.org> > To: nginx-devel@nginx.org > Subject: [PATCH] Add Win32 related files into tar.gz > Message-ID: <20141028.231917.907259224060825208....@cozmixng.org> > Content-Type: text/plain; charset="us-ascii" > > Hi, > > The current nginx can be built with MinGW-w64. Could you add > Win32 related files into tar.gz? If tar.gz includes Win32 > related file, I can build nginx for Windows from tar.gz. > > > Thanks, > -- > kou > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: win32-add-win32-related-files-into-tar-gz.patch > Type: text/x-patch > Size: 986 bytes > Desc: not available > URL: < > http://mailman.nginx.org/pipermail/nginx-devel/attachments/20141028/e15b926d/attachment-0001.bin > > > > ------------------------------ > > Message: 10 > Date: Tue, 28 Oct 2014 14:52:33 +0000 > From: Maxim Dounin <mdou...@mdounin.ru> > To: nginx-devel@nginx.org > Subject: [nginx] Updated OpenSSL used for win32 builds. > Message-ID: > <hg.e40ce16b2c42.1414507953.6026610855610030...@dev.nginx.com> > Content-Type: text/plain; charset="us-ascii" > > details: http://hg.nginx.org/nginx/rev/e40ce16b2c42 > branches: > changeset: 5887:e40ce16b2c42 > user: Maxim Dounin <mdou...@mdounin.ru> > date: Tue Oct 28 17:35:00 2014 +0300 > description: > Updated OpenSSL used for win32 builds. > > diffstat: > > misc/GNUmakefile | 2 +- > 1 files changed, 1 insertions(+), 1 deletions(-) > > diffs (12 lines): > > diff --git a/misc/GNUmakefile b/misc/GNUmakefile > --- a/misc/GNUmakefile > +++ b/misc/GNUmakefile > @@ -5,7 +5,7 @@ NGINX = nginx-$(VER) > TEMP = tmp > > OBJS = objs.msvc8 > -OPENSSL = openssl-1.0.1i > +OPENSSL = openssl-1.0.1j > ZLIB = zlib-1.2.8 > PCRE = pcre-8.35 > > > > > ------------------------------ > > Message: 11 > Date: Tue, 28 Oct 2014 15:17:19 +0000 > From: Maxim Dounin <mdou...@mdounin.ru> > To: nginx-devel@nginx.org > Subject: [nginx] nginx-1.7.7-RELEASE > Message-ID: > <hg.6d2fbc30f8a7.1414509439.6026610855610030...@dev.nginx.com> > Content-Type: text/plain; charset="utf-8" > > details: http://hg.nginx.org/nginx/rev/6d2fbc30f8a7 > branches: > changeset: 5888:6d2fbc30f8a7 > user: Maxim Dounin <mdou...@mdounin.ru> > date: Tue Oct 28 18:04:46 2014 +0300 > description: > nginx-1.7.7-RELEASE > > diffstat: > > docs/xml/nginx/changes.xml | 110 > +++++++++++++++++++++++++++++++++++++++++++++ > 1 files changed, 110 insertions(+), 0 deletions(-) > > diffs (120 lines): > > diff --git a/docs/xml/nginx/changes.xml b/docs/xml/nginx/changes.xml > --- a/docs/xml/nginx/changes.xml > +++ b/docs/xml/nginx/changes.xml > @@ -5,6 +5,116 @@ > <change_log title="nginx"> > > > +<changes ver="1.7.7" date="28.10.2014"> > + > +<change type="change"> > +<para lang="ru"> > +?????? nginx ????????? ??? ??????????? ?????? "Vary" > +? ????????? ?????? ???????. > +</para> > +<para lang="en"> > +now nginx takes into account the "Vary" > +header line in a backend response while caching. > +</para> > +</change> > + > +<change type="feature"> > +<para lang="ru"> > +????????? proxy_force_ranges, fastcgi_force_ranges, > +scgi_force_ranges ? uwsgi_force_ranges. > +</para> > +<para lang="en"> > +the "proxy_force_ranges", "fastcgi_force_ranges", > +"scgi_force_ranges", and "uwsgi_force_ranges" directives. > +</para> > +</change> > + > +<change type="feature"> > +<para lang="ru"> > +????????? proxy_limit_rate, fastcgi_limit_rate, > +scgi_limit_rate ? uwsgi_limit_rate. > +</para> > +<para lang="en"> > +the "proxy_limit_rate", "fastcgi_limit_rate", > +"scgi_limit_rate", and "uwsgi_limit_rate" directives. > +</para> > +</change> > + > +<change type="feature"> > +<para lang="ru"> > +???????? Vary ???????? proxy_ignore_headers, fastcgi_ignore_headers, > +scgi_ignore_headers ? uwsgi_ignore_headers. > +</para> > +<para lang="en"> > +the "Vary" parameter of the "proxy_ignore_headers", > "fastcgi_ignore_headers", > +"scgi_ignore_headers", and "uwsgi_ignore_headers" directives. > +</para> > +</change> > + > +<change type="bugfix"> > +<para lang="ru"> > +????????? ????? ??????, ??????????? ?? ??????? > +??? ?????????????????? ?????????????, > +????? ?? ???????????? ???????, > +???? ?????????????? ????????? gzip ??? gunzip. > +</para> > +<para lang="en"> > +the last part of a response received from a backend > +with unbufferred proxy > +might not be sent to a client > +if "gzip" or "gunzip" directives were used. > +</para> > +</change> > + > +<change type="bugfix"> > +<para lang="ru"> > +? ????????? proxy_cache_revalidate.<br/> > +??????? Piotr Sikora. > +</para> > +<para lang="en"> > +in the "proxy_cache_revalidate" directive.<br/> > +Thanks to Piotr Sikora. > +</para> > +</change> > + > +<change type="bugfix"> > +<para lang="ru"> > +? ????????? ??????.<br/> > +??????? Yichun Zhang ? ??????? ?????????. > +</para> > +<para lang="en"> > +in error handling.<br/> > +Thanks to Yichun Zhang and Daniil Bondarev. > +</para> > +</change> > + > +<change type="bugfix"> > +<para lang="ru"> > +? ?????????? > +proxy_next_upstream_tries ? proxy_next_upstream_timeout.<br/> > +??????? Feng Gu. > +</para> > +<para lang="en"> > +in the "proxy_next_upstream_tries" and "proxy_next_upstream_timeout" > +directives.<br/> > +Thanks to Feng Gu. > +</para> > +</change> > + > +<change type="bugfix"> > +<para lang="ru"> > +nginx/Windows ?? ????????? ? MinGW-w64 gcc.<br/> > +??????? Kouhei Sutou. > +</para> > +<para lang="en"> > +nginx/Windows could not be built with MinGW-w64 gcc.<br/> > +Thanks to Kouhei Sutou. > +</para> > +</change> > + > +</changes> > + > + > <changes ver="1.7.6" date="30.09.2014"> > > <change type="change"> > > ------------------------------ > > _______________________________________________ > nginx-devel mailing list > nginx-devel@nginx.org > http://mailman.nginx.org/mailman/listinfo/nginx-devel > > End of nginx-devel Digest, Vol 60, Issue 34 > ******************************************* > -- Donatas
_______________________________________________ nginx-devel mailing list nginx-devel@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx-devel
