Thank you very much, and sorry for the repeated question. I will dig deeper
before asking next time.
Regards,
Kiril
On Mar 11, 2013, at 1:17 PM, Maxim Dounin wrote:
> Hello!
>
> On Mon, Mar 11, 2013 at 09:58:28AM +0200, Kiril Kalchev wrote:
>
>> After I read the thread, I am wondering what i
Hello!
On Mon, Mar 11, 2013 at 09:58:28AM +0200, Kiril Kalchev wrote:
> After I read the thread, I am wondering what is the recommended way to purge
> nginx cache?
Recommended way is to assume you can't purge the cache, much like
you can't purge caches in client's browsers and/or intermediate
Hello!
After I read the thread, I am wondering what is the recommended way to purge
nginx cache?
Regards,
Kiril
On Mar 10, 2013, at 6:30 PM, Maxim Dounin wrote:
> Hello!
>
> On Sat, Mar 09, 2013 at 07:52:40PM -0500, michael.heuberger wrote:
>
>> Hello guys
>>
>> I'm having this problem too
Hello!
On Sat, Mar 09, 2013 at 07:52:40PM -0500, michael.heuberger wrote:
> Hello guys
>
> I'm having this problem too in version 3.1.14 and never do delete these
> files manually. How can I solve this?
Even if you did not delete files manually, the message still
indicate files were somehow re
Hello guys
I'm having this problem too in version 3.1.14 and never do delete these
files manually. How can I solve this?
Maxim, if you say the message is too scary, then why don't we change the
level of this log message from critical to notice?
Cheers
Michael
Posted at Nginx Forum:
http://foru
