Newsgroups: comp.parallel.mpi From: Kamran Kazemi Subject: Disconnecting Processes In MPI-2.0 Organization: The University Of Western Australia Date: Mon, 02 Mar 1998 13:02:07 +0800 Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="------------057C08E6C607F4D5CEB5B8CB" Message-ID: <34FA3D4E.4448CE8D@cs.uwa.edu.au> --------------057C08E6C607F4D5CEB5B8CB Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Experts of MPI-2.0 standards Two questions 1) MPI_Comm_disconnect of MPI-2.0 standards allows a process to disconnect itself from the communicator. However, it seems that the function call must be collective over the communicator. It means that, in a client/server application the server has to know when the clients want to disconnect. Is there any other way for a process to disconnect itself from a communicator without having to go through a collective call? Is there another routine that would do this? 2) Is it possible for a process to kill other processes? What if they have been spawned by the process itself? Any proposals, solutions, pointers to literature (apart from the MPI-2.0 standards) are much appreciated. Kamran --------------057C08E6C607F4D5CEB5B8CB Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit Experts of MPI-2.0 standards

Two questions

1)    MPI_Comm_disconnect of MPI-2.0 standards  allows a process
to disconnect itself from the communicator.    However, it seems
that the function call must be collective over the communicator.
It means that, in a client/server application  the server has to
know when the clients want to disconnect. Is there any other way
for a process to disconnect itself  from a communicator  without
having to go through a collective call? Is there another routine
that would do this?
 

2)    Is it possible for a process to kill other processes? What
if they have been spawned by the process itself?

Any proposals, solutions, pointers to literature (apart from the
MPI-2.0 standards) are much appreciated.

Kamran --------------057C08E6C607F4D5CEB5B8CB--