From ec64bf3da8d65a3dfefbdc46cf03dbf36db42e88 Mon Sep 17 00:00:00 2001 From: Ralph Castain Date: Wed, 19 Mar 2008 19:06:52 +0000 Subject: [PATCH] Clarify the error output so we can understand if it was a daemon or process that lost its lifeline This commit was SVN r17880. --- orte/mca/oob/tcp/oob_tcp_peer.c | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/orte/mca/oob/tcp/oob_tcp_peer.c b/orte/mca/oob/tcp/oob_tcp_peer.c index ba07dc5850..917f96568f 100644 --- a/orte/mca/oob/tcp/oob_tcp_peer.c +++ b/orte/mca/oob/tcp/oob_tcp_peer.c @@ -585,7 +585,10 @@ void mca_oob_tcp_peer_close(mca_oob_tcp_peer_t* peer) * get stuck in the orte_wait_kill when receiving messages in the * tcp OOB. */ OPAL_THREAD_UNLOCK(&peer->peer_lock); - orte_errmgr.abort(1, "OOB: Connection to lifeline lost"); + opal_output(0, "%s OOB: Connection to lifeline %s lost", + ORTE_NAME_PRINT(ORTE_PROC_MY_NAME), + ORTE_NAME_PRINT(ORTE_PROC_MY_LIFELINE)); + orte_errmgr.abort(1, NULL); } }