Comment 4 for bug 431804

I ended up getting rid of all of it. After more thought I decided that I didn't like init complaining that ufw exited with error. I though it would cause confusion, especially for server users. So the job file is simpler, if ufw is enabled there is no console output (except if an error). If it disabled, it exits 0 and lets you know nothing was done. This is achieved with the following upstart job file:

# ufw - Uncomplicated Firewall
#
# The Uncomplicated Firewall is a front-end for iptables, to make managing a
# Netfilter firewall easier.

description "Uncomplicated firewall"

start on net-device-added INTERFACE=lo
stop on runlevel [!023456]

console output

pre-start exec /lib/ufw/ufw-init start
post-stop exec /lib/ufw/ufw-init stop