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'd also like to re-emphasize something Andreas said earlier: SIGTERM
*usually* means that some external entity is killing your
application. It *could* be coming from within the application itself,
but that's not too common.
You might want to look into that to find out where the SIGTERM is
coming from. The Microtar maintainers might have some better ideas.
On May 30, 2008, at 9:17 AM, Andreas Schäfer wrote:
> On 12:28 Fri 30 May , Lee Amy wrote:
>> 2008/5/29 Andreas Schäfer <gentryx_at_[hidden]>:
>> Thank you very much. If I do a shorter job it seems run well. And
>> the job
>> dosen't repeatedly fail at the same time, but it will fail at this
>> messages. Anyway, I'm not using a scheduling system. So any
> At least no easy ones, sorry. ;-) You could ask the Microtar guys if
> they know anything about that problem. And of course you could use a
> debugger to dig into Microtar and find the problem yourself. ^^ Open
> MPI has some doc how to attach gdb to a parallel job: (and how to use
> valgrind etc.)
> Good luck!
> Andreas Schäfer
> Cluster and Metacomputing Working Group
> Friedrich-Schiller-Universität Jena, Germany
> PGP/GPG key via keyserver
> I'm a bright... http://www.the-brights.net
> This is Bunny. Copy and paste Bunny into your
> signature to help him gain world domination!
> users mailing list