summaryrefslogtreecommitdiff
path: root/packaging
diff options
context:
space:
mode:
authorAlexey Lebedeff <alebedev@mirantis.com>2016-04-22 16:52:42 +0300
committerJean-Sébastien Pédron <jean-sebastien.pedron@dumbbell.fr>2016-04-26 16:51:49 +0200
commit5fb86319c444d459dee3606d56fbde335382f26e (patch)
tree143be685a9b15314c0d291aaad741c721fbe69aa /packaging
parent9099f8b5579d8b8839384bec6c2897df16a6be7e (diff)
downloadrabbitmq-server-git-5fb86319c444d459dee3606d56fbde335382f26e.tar.gz
Improve notifications about damaged I/O subsystem
Follow-up to https://github.com/rabbitmq/rabbitmq-server/pull/747 It's the best thing that can be done. Without `exit` anything inside rabbit could hang - most prone to it is the `start_app` action. Crashing loudly will be helpful, because during 2016 there were at least 2 production investigations about that issue. And here is the script that I was using for reproduction: https://gist.github.com/binarin/edd4102b7262d53e2cf09c76d5ca8e9e
Diffstat (limited to 'packaging')
0 files changed, 0 insertions, 0 deletions