Project

General

Profile

Bug #2697

Hande semicolons in STARTER_JOB_ENVIRONMENT

Added by Burt Holzman over 7 years ago. Updated over 7 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Target version:
Start date:
05/08/2012
Due date:
% Done:

0%

Estimated time:
First Occurred:
Occurs In:
Stakeholders:
Duration:

Description

This is fixed in the semicolon-environ branch -- Parag, please review or assign to an awk expert (that is a lot of backslashes!)

--

"I have run into a problem with a glidein configuration that contains a
semicolon in a value that is to be published into the job environment.
The glideinWMS code that builds STARTER_JOB_ENVIRONMENT uses the old-style
syntax that cannot handle semicolons in environment values:

condor_startup.sh:
if [ -z "$job_env" ]; then
job_env="$var_user=$var_val"
else
job_env="$job_env;$var_user=$var_val"
fi
...
STARTER_JOB_ENVIRONMENT = $job_env

I have attached a patch that uses the new syntax. It can handle semicolons in
the environment. I don't think there are any characters that it can't handle
other than newlines and nulls. The "new style" environment syntax was added
before Condor 7.0, so I am not aware of any relevant backward compatibility
concerns.

--Dan"

History

#1 Updated by Parag Mhashilkar over 7 years ago

  • Status changed from Assigned to Accepted

Looks good to me. Master needs update as well.

#2 Updated by Parag Mhashilkar over 7 years ago

  • Assignee changed from Parag Mhashilkar to Burt Holzman

#3 Updated by Parag Mhashilkar over 7 years ago

  • Status changed from Accepted to Resolved
  • Target version changed from v2_7_x to v2_6

#4 Updated by Parag Mhashilkar over 7 years ago

  • Status changed from Resolved to Closed


Also available in: Atom PDF