Service restart testing nginx.conf
Paul N. Pace
paulnpace at gmail.com
Fri Feb 21 18:36:01 UTC 2014
It seems like way back in the olden days, when I restarted nginx ('sudo
service nginx restart'), if there was a configuration issue in nginx.conf,
I would get a warning telling me such and, IIRC, nginx would boot using the
last known valid configuration.
It doesn't seem to happen that way any more. Did I unknowingly change a
configuration setting, or was there a change to nginx?
Thanks!
Paul
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20140221/1d7ea5b6/attachment.html>
More information about the nginx
mailing list