mirror of
https://github.com/puma/puma.git
synced 2022-11-09 13:48:40 -05:00
Make restart explanation clearer (#1759)
Use the terms used in the explanation in the signals.
This commit is contained in:
parent
1ba884efe7
commit
c96c6d5779
1 changed files with 2 additions and 2 deletions
|
@ -2,8 +2,8 @@
|
|||
|
||||
To perform a restart, there are 3 builtin mechanisms:
|
||||
|
||||
* Send the `puma` process the `SIGUSR2` signal
|
||||
* Send the `puma` process the `SIGUSR1` signal (rolling restart, cluster mode only)
|
||||
* Send the `puma` process the `SIGUSR2` signal (normal restart)
|
||||
* Send the `puma` process the `SIGUSR1` signal (restart in phases (a "rolling restart"), cluster mode only)
|
||||
* Use the status server and issue `/restart`
|
||||
|
||||
No code is shared between the current and restarted process, so it should be safe to issue a restart any place where you would manually stop Puma and start it again.
|
||||
|
|
Loading…
Add table
Reference in a new issue