Random order of configuration file reading
mdounin at mdounin.ru
Wed Nov 28 12:23:00 UTC 2012
On Wed, Nov 28, 2012 at 07:48:27PM +0800, Joshua Zhu wrote:
> On Tue, Nov 27, 2012 at 10:07 PM, philipp <nginx-forum at nginx.us> wrote:
> > Hello,
> > we have a bunch of servers which are configured 100% equal expect of host
> > specific settings like ip address in the listener using chef/puppet. Nginx
> > seems to read include / config files not in the same order on each server.
> > For example we haven't defined a default vhost on each server... so nginx
> > uses the first loaded file which is exampleA.com on server 1 and
> > exampleB.com on server 2.
> > Furhtermore we use the upstream check status module, the status page is
> > randomly ordered at each server...
> > Is it possible to configure nginx to read config in the alphabeticial
> > order?
> > For example
> > vhosts/exampleA.com (1.)
> > vhosts/exampleB.com (2.)
> This is a known issue. It has been fixed in our own
> If you want to use official nginx only, you can apply the patch below:
> Would you please consider to apply this patch to the trunk? Thanks in
I've already proposed removing GLOB_NOSORT to Igor a while ago.
His position on this is to keep this in sync with Windows version
where there is no sort guaranties.
More information about the nginx