ignore bad conf file

Frank Liu gfrankliu at gmail.com
Thu Nov 5 06:33:05 UTC 2015

Thanks Lukas! I tried configtest but with 100k files in conf.d, it takes 3
minutes to finish, during which time there may be another file dropped in
conf.d and trigger another configtest. This sometimes causes several config
test running at the same time.
A reload on the other hand is much quicker and returns almost immediately.
I understand this is just a sighup and nginx internally may still take as
much longer to finish reload? If there is only one file change, will reload
cause nginx to reread all the 100k files and process them ?

On Wednesday, November 4, 2015, Lukas Tribus <luky-37 at hotmail.com> wrote:

> > Hi all,
> >
> > Is there a way to configure nginx to ignore bad conf files?
> No, that would lead to inconsistencies all over the place.
> > My master nginx.conf has a include elsewhere/*.conf towards the end.
> > Other people and programs can drop new configs into "elsewhere"
> > directory. nginx reloads and all is great. Sometimes if one guy drops a
> > conf file with a typo or syntax error, nginx will refuse to reload all
> > other configs afterwards.
> Nginx is supposed to roll back in this case [1], are your reloading (HUP)
> or restarting?
> In any case, testing the config first is what you should do.
> Lukas
> [1] http://nginx.org/en/docs/control.html#reconfiguration
> _______________________________________________
> nginx mailing list
> nginx at nginx.org <javascript:;>
> http://mailman.nginx.org/mailman/listinfo/nginx
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20151104/73f554f9/attachment.html>

More information about the nginx mailing list