Hello.
SIGKILL(9) is not able to trapped for any process.
How about using SIGTERM or QUIT?
Or you might want to see following about controlling nginx with signal.
http://nginx.org/en/docs/control.html
2013/8/8 Vivek Goel
> Hi,
> I am facing one problem with nginx. I am waiting for nginx to
Hi,
I am facing one problem with nginx. I am waiting for nginx to stop withing
30 seconds. If it is not getting stopped, I am firing command to kill
master process using
pkill -9
But, Killing master is not killing the worker process. Due to that reason.
Port is not getting released.
Is it known
Hi,
I'm trying to do the following:
I would like to stop logging from Pingdom bots, as a checking every 5 second
pollutes the access log and it doesn't have any meaningful value. My problem
is that I cannot integrate it into any kind of location block.
I encountered the following errors:
1. map c
Hello,
On Wed, Aug 7, 2013 at 3:09 PM, Roger Pack wrote:
> seems for me that any of these work for showing the virtual host (for
> followers).
>
> $http_host $host $server_name
>
> The Nginx docs specifies different content for those 3 variables.
The $http_host is a subset of the possible valu
seems for me that any of these work for showing the virtual host (for
followers).
$http_host $host $server_name
I just had to uncomment this line for it to 'take', oddly:
#access_log logs/access.log main;
@nginx dev guys: it would be nice if the default config either
mentioned that both
