Core functionality(2)
时间:2019-01-20 05:27 来源:互联网 作者:席子 点击:次
Syntax:
events { ... } Provides the configuration file context in which the directives that affect connection processing are specified.
Syntax:
include file | mask; Includes another file, or files matching the specified mask, into configuration. Included files should consist of syntactically correct directives and blocks. Usage example: include mime.types; include vhosts/*.conf;
Syntax:
load_module file; This directive appeared in version 1.9.11. Loads a dynamic module. Example: load_module modules/ngx_mail_module.so;
Syntax:
lock_file file; nginx uses the locking mechanism to implement and serialize access to shared memory. On most systems the locks are implemented using atomic operations, and this directive is ignored. On other systems the “lock file” mechanism is used. This directive specifies a prefix for the names of lock files.
Syntax:
master_process on | off; Determines whether worker processes are started. This directive is intended for nginx developers.
Syntax:
multi_accept on | off; If multi_accept is disabled, a worker process will accept one new connection at a time. Otherwise, a worker process will accept all new connections at a time. The directive is ignored if connection processing method is used, because it reports the number of new connections waiting to be accepted.
Syntax:
pcre_jit on | off; This directive appeared in version 1.1.12. Enables or disables the use of “just-in-time compilation” (PCRE JIT) for the regular expressions known by the time of configuration parsing. PCRE JIT can speed up processing of regular expressions significantly. The JIT is available in PCRE libraries starting from version 8.20 built with the --enable-jit configuration parameter. When the PCRE library is built with nginx (--with-pcre=), the JIT support is enabled via the --with-pcre-jit configuration parameter.
Syntax:
pid file; Defines a file that will store the process ID of the main process.
Syntax:
ssl_engine device; Defines the name of the hardware SSL accelerator.
Syntax:
thread_pool
name
threads=number
[max_queue=number]; This directive appeared in version 1.7.11. Defines named thread pools used for multi-threaded reading and sending of files worker processes. The threads parameter defines the number of threads in the pool. In the event that all threads in the pool are busy, a new task will wait in the queue. The max_queue parameter limits the number of tasks allowed to be waiting in the queue. By default, up to 65536 tasks can wait in the queue. When the queue overflows, the task is completed with an error. (责任编辑:admin) |
- 上一篇:用“套”有技巧男人须谨慎(图)
- 下一篇:打造你的性爱风格