Mercurial > hg > nginx-site
view xml/en/docs/faq/daemon_master_process_off.xml @ 1826:da6a3e401b26
Slightly reformatted the error_page description.
Information about directives inheritance was moved to the end.
Blocks describing various syntaxes of the "uri" argument were
put in the following order:
- internal redirect to the specified /uri;
- internal redirect to a named location;
- URL redirection.
author | Ruslan Ermilov <ru@nginx.com> |
---|---|
date | Mon, 24 Oct 2016 11:57:46 +0300 |
parents | af3f38e349eb |
children |
line wrap: on
line source
<!-- Copyright (C) Nginx, Inc. --> <!DOCTYPE article SYSTEM "../../../../dtd/article.dtd"> <article name="Can I run nginx with “daemon off” or “master_process off” settings in a production environment?" link="/en/docs/faq/daemon_master_process_off.html" lang="en" rev="1"> <section> <para> <initial>Q:</initial> Can I run nginx with "daemon off" or "master_process off" settings in a production environment? </para> <para> </para> <para> <initial>A:</initial> First of all, both "daemon on|off" and "master_process on|off" directives were intended to be used primarily for nginx code development. </para> <para> While many people use "daemon off" in production it wasn’t really meant for that. Since version 1.0.9 it is now quite safe to run nginx in production with "daemon off", though. Bear in mind that non-stop upgrade is not an option with "daemon off". </para> <para> In a development environment, using "master_process off", nginx can run in the foreground without the master process and can be terminated simply with ^C (SIGINT). This is somewhat similar to running Apache with an 'X' command-line option. However you should NEVER run nginx in production with "master_process off". </para> </section> </article>