| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2012-09-19 | do not disable logging on signal | Scott Moser | |
| I had previously asked for this, but we're hoping to handle it in a more generic way. Just because we receive a signal doesn't mean that all logging is broken. The more general solution we'll chase is to catch a failure of a log message and fall back if necessary across the board. That way cloud-init will still send logging to the right places on a user interupt. | |||
| 2012-09-19 | change exit messages to include signal name | Scott Moser | |
| 2012-09-14 | Add a basic signal test and write out all | Joshua Harlow | |
| the signal information in one block instead of many. | |||
| 2012-09-06 | Fix pylintness. | Joshua Harlow | |
| 2012-09-06 | Add capturing of basic signal handlers to | Joshua Harlow | |
| handle those signals more gracefully and with better messaging than what comes builtin. | |||
