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

Re: [Condor-users] Change in behavior 6.6.0 -> 6.7.1?

On Tue September 14 2004 6:29 am, Chris Green wrote:
> Hi,
> > Could you be a little more specific than "Now, it seems that now it is
> > not!"? Here are a couple of questions that I'd need answered to get a
> > feel for what's going wrong:
> >
> > 1. In what version was this last known to be working?
> 6.6.0
> > 2. Are you seeing that BOONE_LOCAL_SCRATCH is not defined in the job's
> > environment, or that it is defined incorrectly?
> What I am seeing is that BOONE_LOCAL_SCRATCH is defined in the environment
> as the literal string "$$(BOONE_E898_SCRATCH)", rather than the value of
> BOONE_E898_SCRATCH taken from the ClassAd.

Hmm, it seems that you're correct.  Something (probably in the schedd) has 
been changed to affect this.  Actually, my testing reveals that, at least for 
ENV, $$(var) seems completely broken, but it does seem to work, for example, 
with ARGUMENTS. :-(  We need to look into this,  For example.

Here's a test submission:

bash-2.05a$ cat _env.sub
universe = vanilla
#executable = /usr/bin/printenv
executable = env.pl
#env = PATH=/usr/bin:/usr/local/bin;LD_LIBRARY_PATH=/usr/local/lib
env = SPEED=$$(MIPS)
arguments = --disk=$$(DISK) --cpus=$$(CPUS)
output = env.out
log = env.log
error = env.err

And, here's the simple script that it invokes:

bash-2.05a$ cat env.pl
#! /usr/bin/perl -w
use strict;

print "Command line:\n";
foreach my $Arg ( @ARGV )
    print "$Arg\n";
print "Environment:\n";
foreach my $Var ( keys %ENV )
    print "$Var=$ENV{$Var}\n";

And, here's what it produces.  Quite wrong.  :-(

bash-2.05a$ cat env.out
Command line:


           <<< Welcome to the real world. >>>
 /`-_    Nicholas R. LeRoy               The Condor Project
{     }/ http://www.cs.wisc.edu/~nleroy  http://www.cs.wisc.edu/condor
 \    /  nleroy@xxxxxxxxxxx              The University of Wisconsin
 |_*_|   608-265-5761                    Department of Computer Sciences