<div class="gmail_quote">On Fri, Aug 5, 2011 at 04:00, Debao Shao <span dir="ltr"><<a href="mailto:Debao.Shao@brion.com">Debao.Shao@brion.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<p><font size="1" face="宋体"><span lang="EN-US" style="font-size:9.0pt">1, I put
<u></u>"<u></u>PetscInitialize<u></u>"<u></u> at the beginning of main, and
<u></u>"<u></u>PetscInitialize<u></u>"<u></u> registers a signal handler to capture
<u></u>"<u></u>SIGTERM<u></u>"<u></u>;<u></u><u></u></span></font></p>
<p><font size="1" face="宋体"><span lang="EN-US" style="font-size:9.0pt">2, the problem ran in server side will send SIGTERM to kill all of clients after one stage is done.<u></u><u></u></span></font></p>
<p><font size="1" face="宋体"><span lang="EN-US" style="font-size:9.0pt">3, then, unfortunately, the signal
<u></u>"<u></u>SIGTERM<u></u>"<u></u> is caught by the signal handler installed by
<u></u>"<u></u>PetscInitialize<u></u>"<u></u>, and caused to abort.</span></font></p></blockquote></div><div>You can remove the order dependence by running with -no_signal_handler or setting your own signal handler with:</div>
<div><br></div><a href="http://www.mcs.anl.gov/petsc/petsc-as/snapshots/petsc-dev/docs/manualpages/Sys/PetscPushSignalHandler.html">http://www.mcs.anl.gov/petsc/petsc-as/snapshots/petsc-dev/docs/manualpages/Sys/PetscPushSignalHandler.html</a>