Re: [HTCondor-users] execution env in dag

[Jerome Samson <jeromes@xxxxxx>]

Thanks for the answer,

That's actually what I'm working on, but for a large dag it implies 
creating a lot of files to source...

Do you think this might be implemented in future versions ?
Is there a kind of "desired features" poll on htcondor website on which 
I could go to vote for it ? :)

Best,

Jerome
+33 (0) 1 53 06 25 37
---------------------
BUF Compagnie
139-141 Boulevard Ney
75018 Paris
---------------------
Pensez a l'environnement avant d'imprimer ce message


On 05/28/2013 06:27 PM, Nathan Panike wrote:
> On Tue, May 28, 2013 at 06:07:32PM +0200, Jerome Samson wrote:
>    
> > Hi again,
> >
> > I am running a dag and I would like to be able to transfer the env
> > of an executed node to its children, I don't see any correct way to
> > do so in the dag description file.
> >
> > The only thing I'm doing is to set the '-import_env' flag when
> > running condor_submit_dag but it only brings the current env into
> > the dag global environnement.
> > Any other environment variable declared in a particular node is lost
> > for the rest of the dag (particularly for its children).
> >      
> Yep, that is not supported.
>
> If you want to move environment settings around, my suggestion is to
> cause pre scripts or post scripts to write the environment variables
> into the submit file, or cause environment settings to be transferred in
> a file that can be sourced by the job.
>
> Nathan Panike
>
>    
> > Thank's for your help,
> >
> > Jerome Samson
> >      
> _______________________________________________
> HTCondor-users mailing list
> To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
> subject: Unsubscribe
> You can also unsubscribe by visiting
> https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users
>
> The archives can be found at:
> https://lists.cs.wisc.edu/archive/htcondor-users/
>