Mercurial > hg > nginx-site
view xml/en/docs/faq/daemon_master_process_off.xml @ 504:695f83494c19
Emphasized on what the "updating" parameter of the "proxy_cache_use_stale"
directive achieves. Referenced the "proxy_cache_lock" directive from there,
which has similar effect when populating a new cache element.
author | Ruslan Ermilov <ru@nginx.com> |
---|---|
date | Tue, 24 Apr 2012 06:54:47 +0000 |
parents | e58be01b1f4a |
children | be54c443235a |
line wrap: on
line source
<!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"> <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>