Proper setting of read->eof in pipe code. Setting read->eof to 0 seems to be just a typo. It appeared in nginx-0.0.1-2003-10-28-18:45:41 import (r164), while identical code in ngx_recv.c introduced in the same import do actually set read->eof to 1. Failure to set read->eof to 1 results in EOF not being generally detectable from connection flags. On the other hand, kqueue won't report any read events on such a connection since we use EV_CLEAR. This resulted in read timeouts if such connection was cached and used for another request.

ngx_addon_name=ngx_mysql

HTTP_MODULES="$HTTP_MODULES ngx_http_mysql_test_module"

HTTP_INCS="$HTTP_INCS $ngx_addon_dir"
HTTP_DEPS="$HTTP_DEPS $ngx_addon_dir/ngx_mysql.h"
#CORE_LIBS="$CORE_LIBS -lmd"

USE_SHA1=YES

NGX_ADDON_SRCS="$NGX_ADDON_SRCS $ngx_addon_dir/ngx_mysql.c"
NGX_ADDON_SRCS="$NGX_ADDON_SRCS $ngx_addon_dir/ngx_http_mysql_test.c"