This web mail archive is frozen.
This page is part of a frozen web archive of this mailing list.
You can still navigate around this archive, but know that no new mails
have been added to it since July of 2016.
Click here to be taken to the new web archives of this list; it includes all the mails that are in this frozen archive plus all new mails that have been sent to the list since it was migrated to the new archives.
I am encountering the problem that a working child process is frozen in
the middle of its work, and continues only when its parent process (
which spawned it earlier on ) calls some MPI function.
The issue here is, that in order to accept client socket communication
the parent process is, at the same time, performing a select() on a
server socket. It expects the child to finish its work, which will be
collected and processed at a later date. This now cannot happen as the
child does not continue until the parent process calls Recv(), Probe()
or sends something itself.
Is there the possibility that some mpi daemon freezes the child process
if its parent process goes to "sleep" while listening to a socket? If
so, how can I avoid it? These are independent processes and even though
interlinked should not influence each other in this way.