# Unicorn 0.93.4 - \*BSD stdio compatibility **URL:** \ **Category:** Ruby\ **Created:** [October 27, 2009, 10:02am UTC](https://www.ruby-forum.com/t/unicorn-0-93-4-bsd-stdio-compatibility/177964 "2009-10-27T10:02:07Z")\ **Posts on this page:** 1\ **Page:** 1
**Author:** ![ericw](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/e/97f17d/32.png) [@ericw](https://www.ruby-forum.com/u/ericw)\ **Post date:** [October 27, 2009, 10:02am UTC](https://www.ruby-forum.com/t/unicorn-0-93-4-bsd-stdio-compatibility/177964/1 "2009-10-27T10:02:07Z")
Unicorn is a HTTP server for Rack applications designed to only serve fast clients on low-latency, high-bandwidth connections and take advantage of features in Unix/Unix-like kernels. Slow clients should only be served by placing a reverse proxy capable of fully buffering both the the request and response in between Unicorn and slow clients. - [http://unicorn.bogomips.org/](http://unicorn.bogomips.org/) - removed\_email\_address@domain.invalid - git://git.bogomips.org/unicorn.git Changes: This release mainly works around BSD stdio compatibility issues that affect at least FreeBSD and OS X. While this issues was documented and fixed in [ruby-core:26300][1], no production release of MRI 1.8 has it, and users typically upgrade MRI more slowly than gems. This issue does NOT affect 1.9 users. Thanks to Vadim Spivak for reporting and testing this issue and Andrey Stikheev for the fix. Additionally there are small documentation bits, one error handling improvement, and one minor change that should improve reliability of signal delivery. Andrey Stikheev (1): workaround FreeBSD/OSX IO bug for large uploads Eric W. (7): DESIGN: address concerns about on-demand and thundering herd README: alter reply conventions for the mailing list configurator: stop testing for non-portable listens KNOWN\_ISSUES: document Rack gem issue w/Rails 2.3.2 stop continually resends signals during shutdowns add news bodies to site NEWS.atom.xml configurator: fix broken example in RDoc Suraj N. Kurapati (1): show configuration file path in errors instead of ‘(eval)’ [1] [http://redmine.ruby-lang.org/issues/show/2267](http://redmine.ruby-lang.org/issues/show/2267)