Public bug reported: Using Ubuntu 12.04.4 LTS, fully updated.
For this minimal working example: """ $ stress --cpu 2 --timeout 1h --quiet & [1] 10329 $ ps aux | grep stress | grep -v grep petar 10329 0.0 0.0 7236 420 pts/4 S 04:53 0:00 stress --cpu 2 --timeout 1h --quiet petar 10330 101 0.0 7236 96 pts/4 R 04:53 0:13 stress --cpu 2 --timeout 1h --quiet petar 10331 101 0.0 7236 96 pts/4 R 04:53 0:13 stress --cpu 2 --timeout 1h --quiet """ I expect the program to end all its processes on SIGTERM: """ $ kill -TERM 10329 """ however, while the main program does exit, it does not end it's children processes: """ $ ps aux | grep stress | grep -v grep petar 10330 99.8 0.0 7236 96 pts/4 R 04:53 3:33 stress --cpu 2 --timeout 1h --quiet petar 10331 99.8 0.0 7236 96 pts/4 R 04:53 3:33 stress --cpu 2 --timeout 1h --quiet """ The same error occurs with SIGINT. I've created a Docker image based on 'stress' - https://bitbucket.org/petar/docker.cpu_stress_test This bug is preventing Docker from stopping the container properly (using SIGTERM), and instead killing the entire container after a timeout (using SIGKILL). ** Affects: stress (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1335541 Title: stress should handle SIGTERM/SIGINT properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/stress/+bug/1335541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
