Thanks Steven!<br><br>I tried your patch, two chunks rejected, I didn't spend time to figure out the rej diff, but copied that two files from latest nightly build of hydra code. The build didn't fail, but at runtime, there was a Segmentation Fault at the end.<br>
<br>Then I replaced the whole hydra directory with latest build, that worked fine. But this is a much bigger diff than your patch, I would prefer a smaller patch to just fix this problem I have, so I might have to hand-to-hand fix the patch as well.<br>
<br>Limin<br><br><div class="gmail_quote">On Fri, Feb 18, 2011 at 12:33 PM, Steven Sutphen <span dir="ltr"><<a href="mailto:ssutphen@ualberta.ca">ssutphen@ualberta.ca</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Limin,<br>
This sounds like a bug that I helped to track down--in my case mpiexec<br>
blew up in<br>
if I set either of the HYDRA_BOOTSTRAP environment variables. The problem<br>
was that the some of the environment variable handling allocates some<br>
memory that is freed up in some tail code that is common to all the<br>
environment variables the HYDRA_BOOTSTRAP* environment parsing does<br>
not allocate any memory so the pointer used later to free it contains garbage.<br>
Pavan developed a patch that worked for me (after a little hand-to-hand<br>
combat with one chunk of the patch as the patch was not developed with<br>
exactly the same files as were distributed in tarball. I have attached<br>
the patch, but try it at your own discretion.<br>
steve.<br>
<div><div></div><div class="h5"><br>
On Fri, Feb 18, 2011 at 9:47 AM, Pavan Balaji <<a href="mailto:balaji@mcs.anl.gov">balaji@mcs.anl.gov</a>> wrote:<br>
><br>
> Setting the HYDRA_BOOTSTRAP and HYDRA_BOOTSTRAP_EXEC environment variables<br>
> should work. What error are you seeing?<br>
><br>
> Alternatively, you can reconfigure MPICH2 as with<br>
> --with-hydra-bss=rsh,ssh,fork,slurm,ll,lsf,sge,pbs,none,persist<br>
><br>
> This will reprioritize the launchers to give a higher priority to rsh.<br>
><br>
> -- Pavan<br>
><br>
> On 02/18/2011 10:39 AM, Limin Gu wrote:<br>
>><br>
>> Hi,<br>
>><br>
>> I have successfully built and run mpich 1.3.2 on our cluster. But since<br>
>> we rather use bprsh (rsh like) between nodes, I have to specify the<br>
>> bootstrap at mpiexec command line, like this:<br>
>><br>
>> mpiexec -bootstrap rsh -bootstrap-exec /usr/bin/bprsh<br>
>><br>
>> It works, but is there a way that I can make rsh as the default<br>
>> bootstrap in some config file, so I don't have to specify that on every<br>
>> mpiexec command?<br>
>><br>
>> I have tried to set HYDRA_BOOTSTRAP and HYDRA_BOOTSTRAP_EXEC environment<br>
>> variables, that didn't work.<br>
>><br>
>> Thank you!<br>
>><br>
>> Limin<br>
>><br>
>><br>
>><br>
>> _______________________________________________<br>
>> mpich-discuss mailing list<br>
>> <a href="mailto:mpich-discuss@mcs.anl.gov">mpich-discuss@mcs.anl.gov</a><br>
>> <a href="https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss" target="_blank">https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss</a><br>
><br>
> --<br>
> Pavan Balaji<br>
> <a href="http://www.mcs.anl.gov/%7Ebalaji" target="_blank">http://www.mcs.anl.gov/~balaji</a><br>
> _______________________________________________<br>
> mpich-discuss mailing list<br>
> <a href="mailto:mpich-discuss@mcs.anl.gov">mpich-discuss@mcs.anl.gov</a><br>
> <a href="https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss" target="_blank">https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss</a><br>
><br>
><br>
</div></div><br>_______________________________________________<br>
mpich-discuss mailing list<br>
<a href="mailto:mpich-discuss@mcs.anl.gov">mpich-discuss@mcs.anl.gov</a><br>
<a href="https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss" target="_blank">https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss</a><br>
<br></blockquote></div><br>