# Unicorn 1.1.4 - small bug fix and doc updates **URL:** \ **Category:** Ruby\ **Created:** [October 4, 2010, 10:43pm UTC](https://www.ruby-forum.com/t/unicorn-1-1-4-small-bug-fix-and-doc-updates/195990 "2010-10-04T22:43:05Z")\ **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 4, 2010, 10:43pm UTC](https://www.ruby-forum.com/t/unicorn-1-1-4-small-bug-fix-and-doc-updates/195990/1 "2010-10-04T22:43:05Z")
Unicorn is an 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: We no longer unlinking actively listening sockets upon startup (but continue to unlink dead ones). This bug could trigger downtime and nginx failures if a user makes an error and attempts to start Unicorn while it is already running. Thanks to Jordan Ritter for the detailed bug report leading to this fix. ref: [http://mid.gmane.org/removed\_email\_address@domain.invalid](http://mid.gmane.org/removed_email_address@domain.invalid) There are also minor documentation and test updates pulled in from master. This is hopefully the last bugfix release of the 1.1.x series.