Comment 14 for bug 688541

Also attaching the bash script that I used to test this, which simulates a process taking a long time on SIGTERM without forking.. it *should* work with sleep too, given the sendsigs change I posted, but when that change is not there.. sendsigs kills the sleeps and ruins all the fun.

Below is the upstart job I used to run it. I tested this on lucid, 10.04.1, and without the sendsigs change, the script would continue to run right up to the umounts and beyond despite having been "stopped". With the sendsigs change to wait, the test script would be sent SIGKILL well before the end of the halt.

start on filesystem and net-device-up
stop on runlevel [016]

console output

kill timeout 20

exec /home/clint/test_dies_slowly.bash