Using kill signal SIGPWR results in system crash
Bug #1049820 reported by
Christian Kampka
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
upstart |
Fix Released
|
Medium
|
James Hunt |
Bug Description
When using the kill signal stanza to issue a SIGPWR signal ('kill signal 30') to stop a service, it causes the system to crash.
Attached you'll find an upstart script to reproduce the problem.
After calling `stop upstart-pwr`, the system immediately becomes unresponsive, leaving only blinking keyboard lights.
No useful log entries can be found in any of the usual places. Please feel free to ask for any useful information you feel I can provide.
Changed in upstart: | |
status: | New → Confirmed |
assignee: | nobody → James Hunt (jamesodhunt) |
importance: | Undecided → High |
Changed in upstart: | |
status: | Confirmed → Fix Committed |
To post a comment you must log in.
Hi Christian - thank you for reporting this issue. I can see what is causing the issue.
For now, you can work around the problem easily by specifying the signal name:
kill signal SIGPWR