diff options
| author | Max Romanov <max.romanov@gmail.com> | 2022-02-17 12:33:46 +0000 |
|---|---|---|
| committer | Andrew Clayton <andrew@digital-domain.net> | 2022-08-11 13:33:46 +0100 |
| commit | 900828cc4b92e95b4810c00df9759ab9a07429c7 (patch) | |
| tree | 2011d9fa7a2c7c91fda1f27db01c0db6adf0d21e /docs | |
| parent | d37b76232e9b513d109e61e4d5cb562541ed935c (diff) | |
| download | unit-900828cc4b92e95b4810c00df9759ab9a07429c7.tar.gz unit-900828cc4b92e95b4810c00df9759ab9a07429c7.tar.bz2 | |
Fixing isolated process PID manipulation.
Registering an isolated PID in the global PID hash is wrong
because it can be duplicated. Isolated processes are stored only
in the children list until the response for the WHOAMI message is
processed and the global PID is discovered.
To remove isolated siblings, a pointer to the children list is
introduced in the nxt_process_init_t struct.
This closes #633 issue on GitHub.
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/changes.xml | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/docs/changes.xml b/docs/changes.xml index c32716de..f4f5dbf0 100644 --- a/docs/changes.xml +++ b/docs/changes.xml @@ -93,6 +93,13 @@ the ruby application process could crash if it's interrupted by SIGTERM signal. </para> </change> +<change type="bugfix"> +<para> +when isolated PID numbers reach the prototype process host PID, +the prototype crashed. +</para> +</change> + </changes> |