about summary refs log tree commit homepage
path: root/test/http_idle_expire.rb
DateCommit message (Collapse)
2016-05-29update copyrights for 2016
git ls-files | UPDATE_COPYRIGHT_HOLDER='all contributors' \ UPDATE_COPYRIGHT_USE_INTERVALS=2 \ xargs /path/to/gnulib/build-aux/update-copyright
2015-03-06copyright updates for 2015
Via update-copyright in gnulib, also added a few copyrights to non-trivial files. git ls-files | UPDATE_COPYRIGHT_HOLDER='all contributors' \ UPDATE_COPYRIGHT_USE_INTERVALS=2 \ xargs /path/to/gnulib/build-aux/update-copyright
2014-11-02update copyrights to 2014 (and all contributors)
In the future, we can use the update-copyright tool from gnulib: git ls-files | UPDATE_COPYRIGHT_HOLDER='all contributors' \ UPDATE_COPYRIGHT_USE_INTERVALS=2 \ xargs /path/to/gnulib/build-aux/update-copyright This project (nor any project I manage) has or ever will have have copyright assignment. All contributors retain copyrights to their contributions.
2013-02-18copyright comment updates for 2013 (part 2)
Many files were missed the first time around in commit 37026af96dec638aa850d604003bf7218d90037d
2013-02-16test/http_idle_expire: hopefully improve test reliability
This is a tricky test and doesn't always succeed, since it's hard to tell how many file descriptors glibc will use internally.
2012-12-05test/http_idle_expire: skip test if using libkqueue
Different versions of libkqueue may use more or less file descriptors, so skip this Linux-only test for now.
2012-11-12test/http_idle_expire: support testing with libkqueue (under Linux)
Idle expiry still requires Linux TCP_INFO, but we can test with libkqueue.
2012-11-09test/http_idle_expire: disable valgrind for this test
valgrind may create FDs behind our back, throwing off our thresholds for EMFILE/ENFILE.
2012-11-09http: implement idle client expiry under FD pressure
In case there are some wacky setups which open way too many connections, we will nuke old HTTP connections (older than 5 seconds) under high FD pressure. We do not drop connections under normal loads. This costs nothing unless we hit ENFILE/EMFILE/ENOMEM when accepting or opening files. This only affects Linux, but we expect most deployments to be Linux anyways.