Mailing List Archives
Public Access
|
|
|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Condor-users] DAGMan post scripts and ${RETURN}
- Date: Wed, 27 Oct 2004 10:36:33 -0500 (CDT)
- From: Kipp Cannon <kipp@xxxxxxxxxxxxxxxxxxxx>
- Subject: Re: [Condor-users] DAGMan post scripts and ${RETURN}
On Wed, 27 Oct 2004, Peter F. Couvares wrote:
> Kipp Cannon wrote:
> > The Condor user's manual claims that DAGMan will pass the return code
> > from
> > the executable in a DAG node to the post script in that node through a
> > variable called ${RETURN}. Can someone confirm if this claim is
> > correct?
> > ${RETURN} appears to be unset in the post scripts I'm working with...
>
> Kipp,
>
> Just to be clear, DAGMan doesn't set an environment variable named
> RETURN (though that's not a bad idea). Instead, DAGMan will pass the
> job's return code as an argument to your post script if you've
> specified $RETURN as an argument to your script in the DAG
> specification file. E.g.:
>
> Job NodeFoo foo.sub
> Script Post NodeFoo postscript.sh foo bar $RETURN
>
> Or is that what you're doing already?
OOooohhh.... No, that's not what I was doing. I had gotten the impression
that the post script would be run with a variable RETURN set in its
environment. I'll make the change and see how it goes. Thanks.
-Kipp