mirror of
https://gitee.com/openharmony/third_party_nghttp2
synced 2024-11-23 16:00:07 +00:00
Update doc about nghttpx feature
This commit is contained in:
parent
1795d3ea27
commit
fe750240c8
@ -141,6 +141,6 @@ Display this help and exit.
|
||||
.SH AUTHOR
|
||||
Tatsuhiro Tsujikawa
|
||||
.SH COPYRIGHT
|
||||
2012, 2014, Tatsuhiro Tsujikawa
|
||||
2012, 2015, Tatsuhiro Tsujikawa
|
||||
.\" Generated by docutils manpage writer.
|
||||
.
|
||||
|
@ -212,6 +212,6 @@ Display this help and exit.
|
||||
.SH AUTHOR
|
||||
Tatsuhiro Tsujikawa
|
||||
.SH COPYRIGHT
|
||||
2012, 2014, Tatsuhiro Tsujikawa
|
||||
2012, 2015, Tatsuhiro Tsujikawa
|
||||
.\" Generated by docutils manpage writer.
|
||||
.
|
||||
|
@ -157,6 +157,6 @@ Display this help and exit.
|
||||
.SH AUTHOR
|
||||
Tatsuhiro Tsujikawa
|
||||
.SH COPYRIGHT
|
||||
2012, 2014, Tatsuhiro Tsujikawa
|
||||
2012, 2015, Tatsuhiro Tsujikawa
|
||||
.\" Generated by docutils manpage writer.
|
||||
.
|
||||
|
@ -747,8 +747,9 @@ Reopen log files.
|
||||
.TP
|
||||
.B SIGUSR2
|
||||
Fork and execute nghttpx. It will execute the binary in the same
|
||||
path. After new process comes up, sending SIGQUIT to the original
|
||||
process to perform hotswap.
|
||||
path with same command\-line arguments and environment variables.
|
||||
After new process comes up, sending SIGQUIT to the original process
|
||||
to perform hot swapping.
|
||||
.UNINDENT
|
||||
.SH SEE ALSO
|
||||
.sp
|
||||
@ -756,6 +757,6 @@ process to perform hotswap.
|
||||
.SH AUTHOR
|
||||
Tatsuhiro Tsujikawa
|
||||
.SH COPYRIGHT
|
||||
2012, 2014, Tatsuhiro Tsujikawa
|
||||
2012, 2015, Tatsuhiro Tsujikawa
|
||||
.\" Generated by docutils manpage writer.
|
||||
.
|
||||
|
@ -657,8 +657,9 @@ SIGUSR1
|
||||
|
||||
SIGUSR2
|
||||
Fork and execute nghttpx. It will execute the binary in the same
|
||||
path. After new process comes up, sending SIGQUIT to the original
|
||||
process to perform hotswap.
|
||||
path with same command-line arguments and environment variables.
|
||||
After new process comes up, sending SIGQUIT to the original process
|
||||
to perform hot swapping.
|
||||
|
||||
SEE ALSO
|
||||
--------
|
||||
|
@ -19,8 +19,9 @@ SIGUSR1
|
||||
|
||||
SIGUSR2
|
||||
Fork and execute nghttpx. It will execute the binary in the same
|
||||
path. After new process comes up, sending SIGQUIT to the original
|
||||
process to perform hotswap.
|
||||
path with same command-line arguments and environment variables.
|
||||
After new process comes up, sending SIGQUIT to the original process
|
||||
to perform hot swapping.
|
||||
|
||||
SEE ALSO
|
||||
--------
|
||||
|
@ -235,12 +235,12 @@ Read/write rate limit
|
||||
---------------------
|
||||
|
||||
nghttpx supports transfer rate limiting on frontend connections. You
|
||||
can do rate limit per worker (thread) for reading and writeing
|
||||
can do rate limit per frontend connection for reading and writeing
|
||||
individually.
|
||||
|
||||
To rate limit per worker (thread), use ``--worker-read-rate`` and
|
||||
``--worker-read-burst`` options. For writing, use
|
||||
``--worker-write-rate`` and ``--worker-write-burst``.
|
||||
To perform rate limit for reading, use ``--read-rate`` and
|
||||
``--read-burst`` options. For writing, use ``--write-rate`` and
|
||||
``--write-burst``.
|
||||
|
||||
Please note that rate limit is performed on top of TCP and nothing to
|
||||
do with HTTP/2 flow control.
|
||||
@ -263,10 +263,10 @@ precedence. If the above conditions are not met with the host value
|
||||
in :authority header field, rewrite is retried with the value in host
|
||||
header field.
|
||||
|
||||
Hot deploy
|
||||
----------
|
||||
Hot swapping
|
||||
------------
|
||||
|
||||
nghttpx supports hot deploy feature using signals. The hot deploy in
|
||||
nghttpx supports hot swapping using signals. The hot swapping in
|
||||
nghttpx is multi step process. First send USR2 signal to nghttpx
|
||||
process. It will do fork and execute new executable, using same
|
||||
command-line arguments and environment variables. At this point, both
|
||||
|
Loading…
Reference in New Issue
Block a user