shared memory zone "media" conflicts with already declared size 0

[Tomasz Pajor]

Maxim Dounin wrote:
> Hello!
>
> On Tue, Sep 29, 2009 at 11:41:15AM +0200, Tomasz Pajor wrote:
>
>   
>>>>>> what seems to be the problem?
>>>>>>
>>>>>> [emerg]: the size 52428800 of shared memory zone "media"
>>>>>> conflicts with already declared size 0 in
>>>>>> /etc/nginx/conf.d/cache.conf:5
>>>>>> configuration file /etc/nginx/nginx.conf test failed
>>>>>>             
>>>>> This may be caused if "proxy_cache media" is included before proxy_cache_path.
>>>>>           
>>>> this is true,
>>>> in /etc/nginx/conf.d i have two files, cache.conf and ssl.conf,
>>>> and what it seems the ssl.conf is loaded first, shouldn't the
>>>> files be loaded in alphabetical order?
>>>>         
>>> Currently, files are unsorted.
>>> Probably, it should be changed to alphabetical order, but I'm not sure
>>>       
>> I don't know, never the less the desired order can be achieved by
>> adding digits in front of the file name, 001-cache.conf,
>> 002-ssl.conf fixed my issue.
>>     
>
> No, desired order can't be achieved by adding digits.  While using 
> globbed includes nginx loads them without any sorting, i.e. in 
> order how filesystem returns them.
>
> You happened to get correct order after your renames, but things 
> may again go wild at any moment (most likely when you'll touch 
> something in this directory).
>
> Currently the only solution is to include dependent files 
> explicitly.  Globs can be used *only* for completely independent 
> files (e.g. containing definitions of different server{} blocks)
So maybe it is a good idea to add alphabetic order for the wildcard include.