On Dec 30, 2015 12:44 PM, "Gena Makhomed" <g...@csdoc.com> wrote:
>
> On 30.12.2015 19:08, Jim Popovitch wrote:
>
>>> Do you know how nginx and systemd work right now?
>>> You understand race condition between nginx and systemd?
>
>
>&g
On Wed, Dec 30, 2015 at 11:50 AM, Gena Makhomed <g...@csdoc.com> wrote:
> On 30.12.2015 18:09, Jim Popovitch wrote:
>
>>> nginx now requires configured and up network, before starting daemon.
>
>
>> Specifically it's your configuration.
>> You are hardcod
On Wed, Dec 30, 2015 at 10:50 AM, Gena Makhomed wrote:
> nginx now requires configured and up network, before starting daemon.
Specifically it's your configuration. You are hardcoding an IP
address to bind to, thereby telling nginx to not start until that IP
is active.
>
On Tue, Aug 18, 2015 at 12:56 PM, Dmitry xei...@nginx.com wrote:
On 18.08.2015 19:44, Jim Popovitch wrote:
On Tue, Aug 18, 2015 at 12:37 PM, Valentin V. Bartenev vb...@nginx.com
wrote:
On Tuesday 18 August 2015 12:08:12 Jim Popovitch wrote:
On Mon, Aug 17, 2015 at 10:44 AM, Dmitry
On Tue, Aug 18, 2015 at 1:07 PM, Valentin V. Bartenev vb...@nginx.com wrote:
Could you elaborate what exactly is unclear from the docs
with citations? Then we will be able to improve it.
It looks like the docs were just updated, or perhaps I didn't clear my
browser cache often enough. :-)
On Tue, Aug 18, 2015 at 12:37 PM, Valentin V. Bartenev vb...@nginx.com wrote:
On Tuesday 18 August 2015 12:08:12 Jim Popovitch wrote:
On Mon, Aug 17, 2015 at 10:44 AM, Dmitry Volyntsev xei...@nginx.com wrote:
details: http://hg.nginx.org/nginx/rev/b9447fc457b4
branches:
changeset: 6228
On Mon, Aug 17, 2015 at 10:44 AM, Dmitry Volyntsev xei...@nginx.com wrote:
details: http://hg.nginx.org/nginx/rev/b9447fc457b4
branches:
changeset: 6228:b9447fc457b4
user: Dmitry Volyntsev xei...@nginx.com
date: Mon Aug 17 17:42:02 2015 +0300
description:
Sub filter: support of
On Fri, Mar 28, 2014 at 8:20 AM, Maxim Dounin mdou...@mdounin.ru wrote:
Hello!
On Thu, Mar 27, 2014 at 08:18:48PM -0400, Jim Popovitch wrote:
On Thu, Mar 27, 2014 at 1:50 PM, Jim Popovitch jim...@gmail.com wrote:
On Thu, Mar 27, 2014 at 1:27 PM, Maxim Dounin mdou...@mdounin.ru wrote
Hello,
Should proxy_pass retry ipv4 if ipv6 fails? Currently (1.5.12), it
does not, and there is no way to force proxy_pass to always use ipv4.
Specifically, if a proxy_pass host has dual records (A+),
proxy_pass seems to only try the .
I'm considering submitting a patch if there is
On Thu, Mar 27, 2014 at 12:59 PM, Maxim Dounin mdou...@mdounin.ru wrote:
Hello!
On Thu, Mar 27, 2014 at 12:29:03PM -0400, Jim Popovitch wrote:
Should proxy_pass retry ipv4 if ipv6 fails? Currently (1.5.12), it
does not, and there is no way to force proxy_pass to always use ipv4
On Thu, Mar 27, 2014 at 1:27 PM, Maxim Dounin mdou...@mdounin.ru wrote:
Hello!
On Thu, Mar 27, 2014 at 01:12:18PM -0400, Jim Popovitch wrote:
On Thu, Mar 27, 2014 at 12:59 PM, Maxim Dounin mdou...@mdounin.ru wrote:
Hello!
On Thu, Mar 27, 2014 at 12:29:03PM -0400, Jim Popovitch wrote
On Mon, Jan 27, 2014 at 3:02 PM, Valentin V. Bartenev vb...@nginx.com wrote:
http://nginx.org/patches/patch.spdy-v31.txt
This patch upgrades implementation of SPDY protocol in the
ngx_http_spdy_module from draft 2 to draft 3.1.
I am going to commit it at the end of this week. Till then,
Hello,
I'm seeing a strange problem with v1.5.9, the compiled binary is 8
times larger than it was on v1.5.8. My build environment (debian) is
the same that I've used for v1.5.8.
Production:
~$ nginx -V
nginx version: nginx/1.5.8
TLS SNI support enabled
configure arguments: --prefix=/etc/nginx
On Wed, Jan 22, 2014 at 3:23 PM, Ruslan Ermilov r...@nginx.com wrote:
Could it be that you lost some shared library that nginx uses?
For the starters, compare the outputs of file /usr/sbin/nginx
(are both binaries are stripped) and ldd /usr/sbin/nginx (do
they show the same shared libs)?
14 matches
Mail list logo