2017-06-25 11:46:43 +08:00
|
|
|
|
2017-09-05 23:47:48 +08:00
|
|
|
6) 2017.9.5
|
|
|
|
|
6.1) feature: master can wait children to exit with sync or async
|
|
|
|
|
6.2) feature: master can kill SIGTERM children when reloading
|
|
|
|
|
|
2017-08-11 12:15:00 +08:00
|
|
|
5) 2017.8.11
|
|
|
|
|
5.1) safety: master can't fatal for some configure error of any app service.
|
|
|
|
|
|
2017-07-07 15:36:40 +08:00
|
|
|
4) 2017.7.7
|
|
|
|
|
4.1) feature: master can stop or kill one service, stopping service is graceful
|
|
|
|
|
by closing the IPC pipe, and killing service is rude by signal SIGTEM children.
|
|
|
|
|
4.2) feature: add graceful stop API in master's web management interface.
|
|
|
|
|
|
2017-06-26 12:34:23 +08:00
|
|
|
3) 2017.6.26
|
|
|
|
|
3.1) protocol: changed the web management protocols.
|
2017-06-25 11:46:43 +08:00
|
|
|
|
|
|
|
|
2) 2017.6.25
|
|
|
|
|
2.1) feature: acl_master uses kernel event mode
|
|
|
|
|
|
2017-06-18 21:46:52 +08:00
|
|
|
1) 2017.6.18
|
|
|
|
|
1.1) feature: In Docker's running time, the master's pid was set to 1; When
|
|
|
|
|
stopping master by sending TERM singal to master's pid, master_sigdeath func
|
|
|
|
|
will be called and which'll send TERM to -pid that's the master's pid group,
|
|
|
|
|
but in docker the pid is 1, so we should stop the children in the other way.
|
