Red Hat Bugzilla – Bug 63645
Cluadmin doesn't handle SIGTERM
Last modified: 2013-03-06 00:55:28 EST
Description of Problem:
Cluadmin does not exit cleanly when sent a TERM signal - it does not release the
cluster session lock.
Version-Release number of selected component (if applicable): 1.0.11-1
How Reproducible: Always.
Steps to Reproduce:
1. Run cluadmin.
2. Log in on another pty and run "killall -TERM cluadmin"
3. Run cluadmin again.
Nasty message asking if you want to seize the cluster session lock when cluadmin
is run after it's been TERMinated.
Enhancements in pool. As a side effect, I also changed the lack of handling of
Ctrl-C in the same manner, making the UI part of cluadmin *slightly* more sane -
any complete 'commit' operation succeeds, but I also note that signals are
ignored _during_ all operations involving writing the cluster database:
So, in a few instances, "Ctrl-C" will be ignored to prevent data corruption.