Mercurial > hg > nginx-site
view xml/en/docs/faq/daemon_master_process_off.xml @ 2083:fb5eef3637a4
Avoid double negative in if_not_empty.
Use of "not" and "until" in the same sentence makes it confusing.
Moreover, use of "until" with something that doesn't describe an
event or point in time is wrong.
author | Sergey Kandaurov <pluknet@nginx.com> |
---|---|
date | Mon, 11 Dec 2017 19:15:31 +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>