Re: [HTCondor-users] access to $_CONDOR_MACHINE_AD from condor_ssh_to_job

[Gonzalo Merino <gonzalo.merino@xxxxxxxxxxxxxxxx>]

Hi Todd,

No. We did only encounter env vars missing among the ones in your list.

thanks!

Gonzalo

On 17 March 2015 at 17:18, Todd Tannenbaum <tannenba@xxxxxxxxxxx> wrote:

On 3/17/2015 3:44 PM, Gonzalo Merino wrote:

Hello,

Some of our users would like to try and use the condor_ssh_to_job
mechanism for short interactive debugging. We notice though that the
environment one gets after condor_ssh_to_job is quite different than
that of a batch job. For instance, we do not seem to have access
to $_CONDOR_MACHINE_AD

Is there a way to provide this information so that we can configure the
condor_ssh_to_job environment as similar as possible to the batch one?

The intent is for the environment of ssh_to_job to be the same as the batch one. But looking at the code, it appears that the below environment variables are likely to be missing/different between a vanilla batch job and an ssh_to_job session. Did you encounter environment variable differences not on the list below? At any rate, I consider this to be a bug, and assuming the problem is not larger in scope than what I have below, I'll fix it for the next HTCondor release. Thanks for reporting the problem! -Todd

Missing from ssh_to_job compared to a vanilla batch job:
 _CONDOR_MACHINE_AD
 _CONDOR_JOB_AD
 _CONDOR_CHIRP_CONFIG
 _CONDOR_WRAPPER_ERROR_FILE
 _CHIRP_DELAYED_UPDATE_PREFIX

Missing from vanilla batch job compared to ssh_to_job:
 _CONDOR_SLOT_NAME
 _CONDOR_SHELL


_______________________________________________
HTCondor-users mailing list
To unsubscribe, send a message to htcondor-users-request@cs.wisc.edu 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/