+set -
+case "$1" in
+upgrade )
+ /etc/init.d/disorder stop
+ ;;
+failed-upgrade )
+ # Upgrading from 2.0 to 3.0.x can provoke this problem. The 2.0
+ # init script attempts to run disorder(1) but that isn't ready to go
+ # get as users.db has not been created. Therefore old-prerm upgrade
+ # fails and dpkg tries new-prerm failed-upgrade instead.
+ start-stop-daemon -K -q -n disorderd
+ ;;
+esac