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

Update doc

This commit is contained in:
Tatsuhiro Tsujikawa 2016-07-31 20:59:06 +09:00
parent 54f640f3e1
commit d7c9015d8b
2 changed files with 11 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
doc/nghttpx.h2r
View File

@ -49,6 +49,9 @@ SIGQUIT
accepting connection. After all connections are handled, nghttpx accepting connection. After all connections are handled, nghttpx
exits. exits.
SIGHUP
Reload configuration file given in :option:`--conf`.
SIGUSR1 SIGUSR1
Reopen log files. Reopen log files.
@ -56,7 +59,11 @@ 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. path with same command-line arguments and environment variables.
After new process comes up, sending SIGQUIT to the original process After new process comes up, sending SIGQUIT to the original process
to perform hot swapping. to perform hot swapping. The difference between SIGUSR2 + SIGQUIT
and SIGHUP is that former is usually used to execute new binary, and
the master process is newly spawned. On the other hand, the latter
just reloads configuration file, and the same master process
continues to exist.
.. note:: .. note::

3
doc/sources/nghttpx-howto.rst
View File

@ -236,6 +236,9 @@ all existing frontend connections are done, the current process will
exit. At this point, only new nghttpx process exists and serves exit. At this point, only new nghttpx process exists and serves
incoming requests. incoming requests.
If you want to just reload configuration file without executing new
binary, send SIGHUP to nghttpx master process.
Re-opening log files Re-opening log files
-------------------- --------------------