Merge of r4384, r4385: Fixes for limit_rate: *) Fixed throughput problems with large limit_rate. Previous attempt to fix this was in r1658 (0.6.18), though that one wasn't enough (it was a noop). *) Fixed interaction of limit_rate and sendfile_max_chunk. It's possible that configured limit_rate will permit more bytes per single operation than sendfile_max_chunk. To protect disk from takeover by a single client it is necessary to apply sendfile_max_chunk as a limit regardless of configured limit_rate. See here for report (in Russian): http://mailman.nginx.org/pipermail/nginx-ru/2010-March/032806.html

# 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*