[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Condor-users] Trouble overriding TEMP environment variable

One of possible solutions should be to use USER_JOB_WRAPPER.

You can write script in which you export environment variables.
Similar way was used to limiting job resources.

or latest part of page


On Thu, Nov 24, 2011 at 03:12:43PM +0000, Thomas Luff wrote:
> Hi condor-users,
> We use a large set of tools that are downloaded and cached by various jobs. These tools are downloaded to the location as defined by the environment variable $TEMP.
> Unfortunately condor changes this setting to it's own execute directory '/usr/local/condor_x86/local/execute/dir_1585'
> I've tried setting Environment = "TEMP=/tmp" in my job file by it still seems to replace it with it's own setting.
> Has anyone had success overriding these forced environment variables?
> Thanks
> -- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium.  Thank you.
> _______________________________________________
> Condor-users mailing list
> To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with a
> subject: Unsubscribe
> You can also unsubscribe by visiting
> https://lists.cs.wisc.edu/mailman/listinfo/condor-users
> The archives can be found at:
> https://lists.cs.wisc.edu/archive/condor-users/