Feature #246
SIGTERM handler in the AM
| Status: | Assigned | Start: | 18/02/2010 | ||
|---|---|---|---|---|---|
| Priority: | Normal | Due date: | |||
| Assigned to: | Jolyon White | % Done: | 50% |
||
| Category: | OMF Software | ||||
| Target version: | OMF 5.3.1 | Estimated time: | 2.00 hours |
Description
The AM does not react to a SIGTERM signal. It doesn't quit when running "kill PID". Only "kill -9 PID" kills it.
We should implement a signal handler in the AM that cleanly shuts it down when SIGTERM (maybe also CTRL-C? SIGABORT?) is received.
Related issues
| related to Feature #289: AM modifications to use PubSub XMPP messaging | New | 07/05/2010 |
Associated revisions
History
Updated by Christoph Dwertmann 5 months ago
The shutdown function should call stop() for each of the running abstractDaemons. The init.d script must be changed to then send a SIGTERM to the process with the PID we stored and wait for the shutdown (--retry parameter of start-stop-daemon).
Updated by Jolyon White about 1 month ago
- Status changed from New to Assigned
- % Done changed from 0 to 50
- Estimated time set to 2.00
Changed the AM so that it traps SIGTERM and SIGINT and shuts down the service interface cleanly -- but it doesn't shut down the daemons properly yet. I'll do that next. See r582.
Updated by Christoph Dwertmann 13 days ago
- Target version changed from OMF 5.3 to OMF 5.3.1