Description of Problem: In some cases, when the shell which spawned cluadmin is terminated for one reason or another, cluadmin becomes stuck in a _tight_ read-write loop: read(0, "", 1) = 0 write(1, "\7", 1) = -1 EIO (Input/output error) read(0, "", 1) = 0 write(1, "\7", 1) = -1 EIO (Input/output error) read(0, "", 1) = 0 write(1, "\7", 1) = -1 EIO (Input/output error) read(0, "", 1) = 0 ... Version-Release number of selected component (if applicable): 1.0.11, CVS/Development How Reproducible: Sometimes Steps to Reproduce: 1. Run cluadmin 2. Log in to a different terminal. 3. Kill the shell which spawned cluadmin. Actual Results: Cluadmin enters read/write loop, consuming nearly all of the CPU. Expected Results: Cluadmin cleanly exits. Additional Information: Personally, I have been unable to reproduce this problem. I have, however, found the cause of this and implemented code which is now in testing. This bugzilla is mainly for documentation purposes.
Fix in pool.