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 had been using MPICH and its serv_p4 daemon to speed startup times.
I've decided to try OpenMPI (primarily for the fault-tolerance features)
and would like to know what the equivalent of the serv_p4 daemon is.
It appears as though the orted daemon may be what I am after but I don't
quite understand it. I used to run serv_p4 with a specific port number
and then pass a -p4ssport <portnumber> flag to mpirun. The daemon would
remain running on each node and each new mpirun job would simply
communicate directly through a port with the already running instance of
the daemon on that machine and would save the mpirun from having to
launch an rsh. This was great for reducing startup and run times due to
rsh issues. The orted daemon does support a -persistent flag which seems
relevant, but I cannot find a real usage example.
I expect that most of the readers will find this to be a trivial problem
but I'm hoping someone can give me an openmpi equivalent usage example.
Thanks in advance,
818.695.4105, Riverside 146