Re: [HTCondor-users] How to preserve environment variables

[thomas.hartmann@xxxxxxx]

Hi Shkelzen,

might be, that your jobs do not start into a login shell, i.e., that
your environment setup scripts from /etc/profile.d is not sourced.

We run into the same issue and resolved it with help from Max/KIT, i.e.,
starting each job through a very simple job wrapper script on each node [1].

Cheers,
  Thomas

[1]
https://confluence.desy.de/display/grid/Job+Environments


On 04/09/2020 12.01, shkelzen.rugovac@xxxxxxxxx wrote:
> Hi all,
> 
> We are in the process of moving from creamce to htcondorce and we have
> some trouble to pass some basic tests to commissionÂour new htcondorce.
> 
> We set our env variables ( example: $VO_CMS_SW_DIR=/cvmfs/cms.cern.ch
> <http://cms.cern.ch>) using puppet but at the job running time they are
> all unset.
> 
> We know that condor_submit can use getenv for this but we would like to
> have the behaviour of getenv=true to be enabled for the entire cluster
> by default since we do not have a control on jobs that arrived via the
> grid to our site.
> 
> Could someone help in this direction?
> 
> Cheers,
> Shkelzen
> 
> 
> -- 
> Shkelzen RUGOVACÂ Â Â Â srugovac@xxxxxxxxx <mailto:srugovac@xxxxxxxxx>
> 
> Università Libre de Bruxelles
> Bd du Triomphe, CP230
> 1050 Bruxelles - Belgium
> 
> Office at VUB:
> Building G - Level 0 - Room 147
> 
> Tel: (+32) 2 629 33 26
> 
> _______________________________________________
> 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/
>

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature