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.

# Copyright (C) Igor Sysoev


echo $ngx_n "checking for $ngx_lib ...$ngx_c"

cat << END >> $NGX_AUTOCONF_ERR

----------------------------------------
checking for $ngx_lib

END

ngx_found=no

cat << END > $NGX_AUTOTEST.c

$ngx_lib_incs

int main() {
    $ngx_lib_test;
    return 0;
}


eval "$CC $cc_test_flags $ngx_lib_cflags \
     -o $NGX_AUTOTEST $NGX_AUTOTEST.c $ngx_libs \
     >> $NGX_ERR 2>&1"

if [ -x $NGX_AUTOTEST ]; then
    echo " found"

    ngx_found=yes

else
    echo " not found"
fi

rm $NGX_AUTOTEST*