I've removed it because I added the ```check_status``` function, which I don't want to cause the script to exit if it returns a 1. Also, from [here](http://www.debian.org/doc/debian-policy/ch-opersys.html):

>Be careful of using ```set -e``` in ```init.d``` scripts. Writing correct ```init.d``` scripts requires accepting various error exit statuses when daemons are already running or already stopped without aborting the ```init.d``` script, and common ```init.d``` function libraries are not safe to call with ```set -e``` in effect. For ```init.d``` scripts, it's often easier to not use set -e and instead check the result of each command separately.

As I updated the script, I found that in most cases I didn't actually want the effects of ```set -e```. You'll see that further down I've enabled ```set -e``` in the few cases where I do want the script to exit on an error, and in other cases I've tried to handle errors appropriately.

At some point I'd like to revisit this script and rewrite it using ```/lib/lsb/init-functions``` functions instead of ```echo``` (functions like ```log_action_msg``` and ```log_end_msg```). At that point I'd probably get rid of ```set -e``` altogether, as I wouldn't want it to conflict with these functions. In fact, now that I do a little more reading about using ```set -e``` in ```init.d``` scripts, I think I might get rid of ```set -e``` entirely for this pull request.