Large buffers can hurt as well as help.  And the difference
in real apps that do a lot of things other than I/O often
makes it not worth it.

Rails 3 is out, and requires no code changes on our end to work
(as far as our tests show :)

These nasty hacks were breaking Rubinius compatibility.
This can be further cleaned up, too.

* 1.1.x-stable:
  unicorn 1.1.3 - small bug fixes
  make log reopens even more robust in threaded apps
  update Rails3 tests to use 3.0.0rc2
  make log reopens more robust in multithreaded apps
  bin/*: more consistent --help output
  SIGTTIN works after SIGWINCH

This release fixes race conditions during SIGUSR1 log cycling.
This bug mainly affects Rainbows! users serving static files,
but some Rack apps use threads internally even under Unicorn.

Other small fixes:
* SIGTTIN works as documented after SIGWINCH
* --help output from `unicorn` and `unicorn_rails` is more consistent

A follow-up to 4b23693b9082a84433a9e6c1f358b58420176b27

If multithreaded programming can be compared to juggling
chainsaws, then multithreaded programming with signal handlers
in play is akin to juggling chainsaws on a tightrope
over shark-infested waters.
(cherry picked from commit feab35fe531843066db3418598874cf9f9419614)

A follow-up to 4b23693b9082a84433a9e6c1f358b58420176b27

If multithreaded programming can be compared to juggling
chainsaws, then multithreaded programming with signal handlers
in play is akin to juggling chainsaws on a tightrope
over shark-infested waters.

No code changes needed, thankfully.
(cherry picked from commit 18968f6aff2fa5ba5a7e3e3d47c9cc05cd6c260d)

No code changes needed, thankfully.

IOError may occur due to race conditions as another thread
may close the file immediately after we call File#closed?
to check.

Errno::EBADF may occur in some applications that close a file
descriptor without notifying Ruby (or if two IO objects refer to
the same descriptor, possibly one of them using IO#for_fd).
(cherry picked from commit 4b23693b9082a84433a9e6c1f358b58420176b27)