ignore bad conf file
gfrankliu at gmail.com
Tue Nov 3 21:23:25 UTC 2015
Is there a way to configure nginx to ignore bad conf files?
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. Is it possible to configure nginx to skip the bad file and move
on to next *.conf?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the nginx