walkero
/
nghttp2
1
0
Fork 0
Code Issues Pull Requests Projects Releases 1 Wiki Activity

Update manual pages

This commit is contained in:
Tatsuhiro Tsujikawa 2021-07-18 14:08:52 +09:00
parent 1b6f547948
commit 31253f400d
5 changed files with 34 additions and 34 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/h2load.1
View File

@ -1,6 +1,6 @@
.\" Man page generated from reStructuredText. .\" Man page generated from reStructuredText.
. .
.TH "H2LOAD" "1" "Jul 18, 2021" "1.44.0" "nghttp2" .TH "H2LOAD" "1" "Jul 18, 2021" "1.45.0-DEV" "nghttp2"
.SH NAME .SH NAME
h2load \- HTTP/2 benchmarking tool h2load \- HTTP/2 benchmarking tool
. .

2
doc/nghttp.1
View File

@ -1,6 +1,6 @@
.\" Man page generated from reStructuredText. .\" Man page generated from reStructuredText.
. .
.TH "NGHTTP" "1" "Jul 18, 2021" "1.44.0" "nghttp2" .TH "NGHTTP" "1" "Jul 18, 2021" "1.45.0-DEV" "nghttp2"
.SH NAME .SH NAME
nghttp \- HTTP/2 client nghttp \- HTTP/2 client
. .

2
doc/nghttpd.1
View File

@ -1,6 +1,6 @@
.\" Man page generated from reStructuredText. .\" Man page generated from reStructuredText.
. .
.TH "NGHTTPD" "1" "Jul 18, 2021" "1.44.0" "nghttp2" .TH "NGHTTPD" "1" "Jul 18, 2021" "1.45.0-DEV" "nghttp2"
.SH NAME .SH NAME
nghttpd \- HTTP/2 server nghttpd \- HTTP/2 server
. .

32
doc/nghttpx.1
View File

@ -1,6 +1,6 @@
.\" Man page generated from reStructuredText. .\" Man page generated from reStructuredText.
. .
.TH "NGHTTPX" "1" "Jul 18, 2021" "1.44.0" "nghttp2" .TH "NGHTTPX" "1" "Jul 18, 2021" "1.45.0-DEV" "nghttp2"
.SH NAME .SH NAME
nghttpx \- HTTP/2 proxy nghttpx \- HTTP/2 proxy
. .
@ -1784,15 +1784,15 @@ Error log is written to stderr by default. It can be configured
using \fI\%\-\-errorlog\-file\fP\&. The format of log message is as using \fI\%\-\-errorlog\-file\fP\&. The format of log message is as
follows: follows:
.sp .sp
<datetime> <master\-pid> <current\-pid> <thread\-id> <level> (<filename>:<line>) <msg> <datetime> <main\-pid> <current\-pid> <thread\-id> <level> (<filename>:<line>) <msg>
.INDENT 7.0 .INDENT 7.0
.TP .TP
.B <datetime> .B <datetime>
It is a combination of date and time when the log is written. It It is a combination of date and time when the log is written. It
is in ISO 8601 format. is in ISO 8601 format.
.TP .TP
.B <master\-pid> .B <main\-pid>
It is a master process ID. It is a main process ID.
.TP .TP
.B <current\-pid> .B <current\-pid>
It is a process ID which writes this log. It is a process ID which writes this log.
@ -1828,15 +1828,15 @@ SIGUSR2
.INDENT 3.5 .INDENT 3.5
Fork and execute nghttpx. It will execute the binary in the same Fork and execute nghttpx. It will execute the binary in the same
path with same command\-line arguments and environment variables. As path with same command\-line arguments and environment variables. As
of nghttpx version 1.20.0, the new master process sends SIGQUIT to of nghttpx version 1.20.0, the new main process sends SIGQUIT to the
the original master process when it is ready to serve requests. For original main process when it is ready to serve requests. For the
the earlier versions of nghttpx, user has to send SIGQUIT to the earlier versions of nghttpx, user has to send SIGQUIT to the
original master process. original main process.
.sp .sp
The difference between SIGUSR2 (+ SIGQUIT) and SIGHUP is that former The difference between SIGUSR2 (+ SIGQUIT) and SIGHUP is that former
is usually used to execute new binary, and the master process is is usually used to execute new binary, and the main process is newly
newly spawned. On the other hand, the latter just reloads spawned. On the other hand, the latter just reloads configuration
configuration file, and the same master process continues to exist. file, and the same main process continues to exist.
.UNINDENT .UNINDENT
.UNINDENT .UNINDENT
.sp .sp
@ -1845,16 +1845,16 @@ configuration file, and the same master process continues to exist.
.INDENT 3.5 .INDENT 3.5
nghttpx consists of multiple processes: one process for processing nghttpx consists of multiple processes: one process for processing
these signals, and another one for processing requests. The former these signals, and another one for processing requests. The former
spawns the latter. The former is called master process, and the spawns the latter. The former is called main process, and the
latter is called worker process. If neverbleed is enabled, the latter is called worker process. If neverbleed is enabled, the
worker process spawns neverbleed daemon process which does RSA key worker process spawns neverbleed daemon process which does RSA key
processing. The above signal must be sent to the master process. processing. The above signal must be sent to the main process. If
If the other processes received one of them, it is ignored. This the other processes received one of them, it is ignored. This
behaviour of these processes may change in the future release. In behaviour of these processes may change in the future release. In
other words, in the future release, the processes other than master other words, in the future release, the processes other than main
process may terminate upon the reception of these signals. process may terminate upon the reception of these signals.
Therefore these signals should not be sent to the processes other Therefore these signals should not be sent to the processes other
than master process. than main process.
.UNINDENT .UNINDENT
.UNINDENT .UNINDENT
.SH SERVER PUSH .SH SERVER PUSH

30
doc/nghttpx.1.rst
View File

@ -1625,14 +1625,14 @@ Error log
using :option:`--errorlog-file`. The format of log message is as using :option:`--errorlog-file`. The format of log message is as
follows: follows:
<datetime> <master-pid> <current-pid> <thread-id> <level> (<filename>:<line>) <msg> <datetime> <main-pid> <current-pid> <thread-id> <level> (<filename>:<line>) <msg>
<datetime> <datetime>
It is a combination of date and time when the log is written. It It is a combination of date and time when the log is written. It
is in ISO 8601 format. is in ISO 8601 format.
<master-pid> <main-pid>
It is a master process ID. It is a main process ID.
<current-pid> <current-pid>
It is a process ID which writes this log. It is a process ID which writes this log.
@ -1665,30 +1665,30 @@ SIGUSR2
Fork and execute nghttpx. It will execute the binary in the same Fork and execute nghttpx. It will execute the binary in the same
path with same command-line arguments and environment variables. As path with same command-line arguments and environment variables. As
of nghttpx version 1.20.0, the new master process sends SIGQUIT to of nghttpx version 1.20.0, the new main process sends SIGQUIT to the
the original master process when it is ready to serve requests. For original main process when it is ready to serve requests. For the
the earlier versions of nghttpx, user has to send SIGQUIT to the earlier versions of nghttpx, user has to send SIGQUIT to the
original master process. original main process.
The difference between SIGUSR2 (+ SIGQUIT) and SIGHUP is that former The difference between SIGUSR2 (+ SIGQUIT) and SIGHUP is that former
is usually used to execute new binary, and the master process is is usually used to execute new binary, and the main process is newly
newly spawned. On the other hand, the latter just reloads spawned. On the other hand, the latter just reloads configuration
configuration file, and the same master process continues to exist. file, and the same main process continues to exist.
.. note:: .. note::
nghttpx consists of multiple processes: one process for processing nghttpx consists of multiple processes: one process for processing
these signals, and another one for processing requests. The former these signals, and another one for processing requests. The former
spawns the latter. The former is called master process, and the spawns the latter. The former is called main process, and the
latter is called worker process. If neverbleed is enabled, the latter is called worker process. If neverbleed is enabled, the
worker process spawns neverbleed daemon process which does RSA key worker process spawns neverbleed daemon process which does RSA key
processing. The above signal must be sent to the master process. processing. The above signal must be sent to the main process. If
If the other processes received one of them, it is ignored. This the other processes received one of them, it is ignored. This
behaviour of these processes may change in the future release. In behaviour of these processes may change in the future release. In
other words, in the future release, the processes other than master other words, in the future release, the processes other than main
process may terminate upon the reception of these signals. process may terminate upon the reception of these signals.
Therefore these signals should not be sent to the processes other Therefore these signals should not be sent to the processes other
than master process. than main process.
SERVER PUSH SERVER PUSH
----------- -----------