LAM/MPI logo

LAM/MPI General User's Mailing List Archives

  |   Home   |   Download   |   Documentation   |   FAQ   |   all just in this list

From: YoungHui Amend (yamend_at_[hidden])
Date: 2006-06-15 19:22:10


I'm running mpirun with application schema file so, the stdout/stderr
redirections are being interpreted as parameters to the TWTgenfm
command.

this is my mpirun command:
mpirun -ssi rpi tcp $applicationSchemafile

Here's my application schema file:
n0 TWTgen parallelprocess=yes experiment=ya switchppatratio=0.2 lapgs=no
n1 TWTgenfm experiment=ya switchppatratio=0.2 lapgs=no 2>&1 >
/tmp/lam_out.29805.1
n2 TWTgenfm experiment=ya switchppatratio=0.2 lapgs=no 2>&1 >
/tmp/lam_out.29805.2

Any other suggestion???

-----Original Message-----
From: lam-bounces_at_[hidden] [mailto:lam-bounces_at_[hidden]] On Behalf
Of Phil Ehrens
Sent: Thursday, June 15, 2006 3:39 PM
To: General LAM/MPI mailing list
Subject: Re: LAM: Redirect stdout in remotes nodes

That is essentially what I do, but my wrapper is somewhat more
sophisticated, opening pipes to ssh processes instead of files. I have
no problem managing several thousand jobs per hour for months on end.
The canonical ssh invocation for this sort of thing is:

ssh -x -n -obatchmode=yes -oconnectimeout=2 $usr@$host $cmd 2>@stdout

I used Tcl for the wrapper because I could leverage it's event loop for
asynchronous error handling by parsing the return values from the
command incrementally.

Note that top-posting makes things harder to read, but since you started
it (John) I can blame you ;^)

John Robinson wrote:
> On about a microsecond's thought, but how about if you create a shell
> script wrapper that takes the target app name and its args as its
> arguments, and then does an exec of it after directing stdout and
> stderr to files.
>
> This simple shellscript gets at the idea:
>
> exec $* 2>$1.stderr >$1.stdout
> ---
> YoungHui Amend wrote:
> >
> > There's alot of code (developed by many people) that are executed
> > for each application call. So, printing to a log file (fprinf) is
> > not an option (unfortunately). Is there something I can do with
> > lamboot or mpirun to redirect the stdout/stderr?
_______________________________________________
This list is archived at http://www.lam-mpi.org/MailArchives/lam/