# Unicorn 1.0.1 and 1.1.2 - fix rollbacks

**URL:** <https://www.ruby-forum.com/t/unicorn-1-0-1-and-1-1-2-fix-rollbacks/191523>\
**Category:** Ruby\
**Created:** [July 13, 2010, 10:13pm UTC](https://www.ruby-forum.com/t/unicorn-1-0-1-and-1-1-2-fix-rollbacks/191523 "2010-07-13T22:13:23Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**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:** [July 13, 2010, 10:13pm UTC](https://www.ruby-forum.com/t/unicorn-1-0-1-and-1-1-2-fix-rollbacks/191523/1 "2010-07-13T22:13:23Z")

</div>

Changes:

Theses release fix a long-standing bug where the original PID  
file is not restored when rolling back from a USR2 upgrade.  
Presumably most upgrades aren’t rolled back, so it took over a  
year to notice this issue. Thanks to Lawrence P. for  
discovering and reporting this issue.

About Unicorn:

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
