Welcome! Log In Create A New Profile

Advanced

Re: $time_iso8601 is not set for invalid HTTP?

Maxim Dounin
December 01, 2014 10:56AM
Hello!

On Mon, Dec 01, 2014 at 08:23:53AM -0500, igorb wrote:

> > avoid using such "timestamped log names" at all as this approach implies
> unneeded overhead on opening/closing files for each request.
>
> I use open_log_file_cache to mitigate this. Are there still problems with
> that? I would prefer to keep things simple and avoid explicit log rotation.

While open_log_file_cache mitigates most of the overhead involved,
this still implies constructing a log file name for each request,
looking up this name in the cache and so on. It's still better to
use explicitly specified log file names.

--
Maxim Dounin
http://nginx.org/

_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Subject Author Posted

$time_iso8601 is not set for invalid HTTP?

igorb November 29, 2014 03:48PM

Re: $time_iso8601 is not set for invalid HTTP?

Maxim Dounin December 01, 2014 07:54AM

Re: $time_iso8601 is not set for invalid HTTP?

igorb December 01, 2014 08:23AM

Re: $time_iso8601 is not set for invalid HTTP?

Maxim Dounin December 01, 2014 10:56AM

Re: $time_iso8601 is not set for invalid HTTP?

Darren Pilgrim December 01, 2014 11:26AM

Re: $time_iso8601 is not set for invalid HTTP?

Oleksandr V. Typlyns'kyi December 01, 2014 12:42PM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 312
Record Number of Users: 8 on April 13, 2023
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready