>> you are right. There is a problem:
>>
>> https://bugs.gentoo.org/show_bug.cgi?id=473036
>>
>> Upstream (nginx) accepted the report:
>> http://trac.nginx.org/nginx/ticket/376
>
> The "accepted" part is about future enhancement. The Gentoo part
> seems to be about wrong permissions on a log direc
Hello!
On Thu, Jul 18, 2013 at 03:14:10PM +0200, Igor Sverkos wrote:
> Hi,
>
> you are right. There is a problem:
>
> https://bugs.gentoo.org/show_bug.cgi?id=473036
>
> Upstream (nginx) accepted the report:
> http://trac.nginx.org/nginx/ticket/376
The "accepted" part is about future enhanceme
> you are right. There is a problem:
>
> https://bugs.gentoo.org/show_bug.cgi?id=473036
>
> Upstream (nginx) accepted the report:
> http://trac.nginx.org/nginx/ticket/376
Many thanks Igor! You've saved me a lot of trouble.
- Grant
___
nginx mailing li
Hi,
you are right. There is a problem:
https://bugs.gentoo.org/show_bug.cgi?id=473036
Upstream (nginx) accepted the report:
http://trac.nginx.org/nginx/ticket/376
--
Regards,
Igor
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mail
>> I noticed that most of my rotated nginx log files are empty (0 bytes).
>>
>> My only access_log directive is in nginx.conf:
>>
>> access_log /var/log/nginx/localhost.access_log combined;
>>
>> Also nginx is currently logging to
>> /var/log/nginx/localhost.access_log.1 instead of localhost.access
>> Any other ideas?
>
> Not sure if relevant, but in Gentoo's bug tracker are some open bugs
> regarding current logrotate versions:
>
> https://bugs.gentoo.org/show_bug.cgi?id=476202
> https://bugs.gentoo.org/show_bug.cgi?id=474572
> https://bugs.gentoo.org/show_bug.cgi?id=476720
>
> Seems to be u
Hi,
> Any other ideas?
Not sure if relevant, but in Gentoo's bug tracker are some open bugs
regarding current logrotate versions:
https://bugs.gentoo.org/show_bug.cgi?id=476202
https://bugs.gentoo.org/show_bug.cgi?id=474572
https://bugs.gentoo.org/show_bug.cgi?id=476720
Seems to be upstream bug
>> >> I noticed that most of my rotated nginx log files are empty (0 bytes).
>> >>
>> >> My only access_log directive is in nginx.conf:
>> >>
>> >> access_log /var/log/nginx/localhost.access_log combined;
>> >>
>> >> Also nginx is currently logging to
>> >> /var/log/nginx/localhost.access_log.1 ins
Hello!
On Mon, Jul 15, 2013 at 02:49:47AM -0700, Grant wrote:
> >> I noticed that most of my rotated nginx log files are empty (0 bytes).
> >>
> >> My only access_log directive is in nginx.conf:
> >>
> >> access_log /var/log/nginx/localhost.access_log combined;
> >>
> >> Also nginx is currently l
>> I noticed that most of my rotated nginx log files are empty (0 bytes).
>>
>> My only access_log directive is in nginx.conf:
>>
>> access_log /var/log/nginx/localhost.access_log combined;
>>
>> Also nginx is currently logging to
>> /var/log/nginx/localhost.access_log.1 instead of localhost.access
Hello!
On Sun, Jul 14, 2013 at 04:44:53AM -0700, Grant wrote:
> I noticed that most of my rotated nginx log files are empty (0 bytes).
>
> My only access_log directive is in nginx.conf:
>
> access_log /var/log/nginx/localhost.access_log combined;
>
> Also nginx is currently logging to
> /var/l
I noticed that most of my rotated nginx log files are empty (0 bytes).
My only access_log directive is in nginx.conf:
access_log /var/log/nginx/localhost.access_log combined;
Also nginx is currently logging to
/var/log/nginx/localhost.access_log.1 instead of localhost.access_log.
Does anyone kn
12 matches
Mail list logo
