view xml/en/docs/faq/daemon_master_process_off.xml @ 198:ec4626d04879

- Bulk commit following discussion in devrep
author Andrey Alexeev <andrew@nginx.com>
date Wed, 23 Nov 2011 16:31:50 +0000
parents aafe530e7d6f
children 19c060caf965
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>
&nbsp;
</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 develpment.
</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' commandline option. However you should NEVER run nginx in production
with "master_process off".
</para>

</section>

</article>