Core functionality

Directives

force_exit

Syntax: force_exit exit_time;

Default: —

Context: main

force worker processes to exit after exit_time.

The force_exit support is not enabled by default. You should compile it explicitly:

 ./configure --with-force-exit

Note: Removed force_exit directive after the Tengine-2.3.0 version and use Nginx official worker_shutdown_timeout , detailed reference worker_shutdown_timeout

worker_processes

Syntax: worker_processes [num | auto]

Default: worker_processes auto

Context: main

Set the number of worker processes. When set to 'auto', which is also the default behavior, Tengine will create the same number of worker processes as your CPUs.

master_env

Syntax: master_env variable[=value];

Default: -

Context: main

If use master_env directive to set NGX_DNS_RESOLVE_BACKUP_PATH environment variable and dns cache will be enabled. When the dns server is unavailable, it's will use the last dns cache.

For example master_env NGX_DNS_RESOLVE_BACKUP_PATH=/home/tengine/worker/dnscache/path, the domain A record results will be saved to the file and path depends on NGX_DNS_RESOLVE_BACKUP_PATH.

worker_cpu_affinity

Syntax: worker_cpu_affinity [mask1 mask2 mask3 ... | auto | off] Default: worker_cpu_affinity off Context: main

Bind worker processes to the sets of CPUs. When set to 'auto', Tengine will automatically bind each worker process to a specific CPU. If the number of worker processes is larger than the number of your CPUs, then the rest of worker processes will be bond in descendant order. For example, if there are 8 CPUs in your system:

When the process number set to 4, the binding bitmap will be:

10000000 01000000 00100000 00010000
When the process number set to 8, the binding bitmap will be:

10000000 01000000 00100000 00010000 00001000 00000100 00000010 00000001
When the process number set to 10, the binding bitmap will be:

10000000 01000000 00100000 00010000 00001000 00000100 00000010 00000001 10000000 01000000

When set to 'off', Tengine will disable the CPU affinity.

error_page

Syntax: error_page code ... [default] [=[response]]

Default: -

Context: http, server, location, if in location

This directive can specify the page for the specific HTTP response status.

Tengine also has a 'default' parameter which can be used to clear the error_page settings in higher level blocks.

For example:

    http {
        error_page 404 /404.html;

        server {
            error_page 404 default;
        }
    }

In this server block, the 404 error page will be set to Tengine's default 404 page.