nginx.conf
worker_processes 4
I add some log and print to monitor like this:
nginx: [emerg] Out LOOP start:08A848A8, b->pos:08A848B9, alloc:18 bytes, word->data:worker_processes,len(word->data):16 in /usr/local/nginx/conf/nginx.conf:3
nginx: [emerg] Out LOOP start:08A848BA, b->pos:08A848BC, alloc:3 bytes, word->data:4,len(word->data):1 in /usr/local/nginx/conf/nginx.conf:3
"worker_processes" need 16+1 bytes, but alloced 18bytes
"4" need 1+1 bytes, byt alloced 3 bytes
In a binary tree deletion, as its defination, first we need to find the
minimum node of its right sub-tree to replace the location of the node
to be deleted when it has both its left and right children. Then we
shall trace its sub-tree to find the minimum node in `ngx_rbtree_min`
function. Since the terminal condition of the tracing loop has already
been set as `node->left == sentinel`, there is no need to leave the
following if-condition judging whether the substitute node's left child
is the sentinel any more because the program will never run here. And the
code will be cleaner as well as may run even faster in some situations
after removing this redundant conditional branch.
In C++ SGI STL stl_tree.c source, we can see there is no if-condition
judgement in rbtree deletion:
https://github.com/dutor/stl/blob/master/sgi/stl_tree.h#L317
By the way, the current released Nginx source still has this issue but
I have no idea how to commit this patch to the project.
Signed-off-by: Leo Ma <begeekmyfriend@gmail.com>
This directive is used to set some locations avoiding
client certificate verfication. If you turn on this
directive in one location, this location will not be
affected by the ssl_verify_client directive upper level.
Signed-off-by: Paul Yang <paulyang.inf@gmail.com>