Version: 1
-Previous: 64a53ecd56cf912dc24205f47bded1c908b6eb3f
-Head: ff42af176a48b5f5970d9304a40ce6d3295d36ba
+Previous: e8a94c69165d72c89711b6ef8e6a2b0f0b9b3107
+Head: b7c0d6fa456b89ef69335c043075ef8142e7787b
Applied:
af-ib-conn: 79a9408f96fbb36a7ef479e8f1568bfd70e1f32d
addrtype: ff42af176a48b5f5970d9304a40ce6d3295d36ba
+ ucmatose: b7c0d6fa456b89ef69335c043075ef8142e7787b
Unapplied:
dbg-fork: 5679a32af8305db3c0406f9abb961259304a384a
dbg-out: 4b4c0572eab77856d8fbb919b1feb8f3502a101a
--- /dev/null
+Bottom: 292961092e4e0812d3138390081aa46cab16ba2b
+Top: 292961092e4e0812d3138390081aa46cab16ba2b
+Author: Sean Hefty <sean.hefty@intel.com>
+Date: 2012-10-04 11:49:59 -0700
+
+ucmatose: Fix number of connections to disconnect
+
+When ucmatose aborts because of issues trying to connect
+to the server, it moves to disconnecting all connections.
+However, not all connections may have been established.
+The result is that ucmatose will hang in disconnect_events.
+Fix this by setting the number of times that we need to
+disconnect to the number of times that we successfully
+connect.
+
+This problem is based on a report by Doug Ledford
+<dledford@redhat.com>
+
+Signed-off-by: Sean Hefty <sean.hefty@intel.com>
+
+
+---
+
+