Mailing List Archives
Authenticated access
|
|
|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Condor-users] Environment problems in submit files
- Date: Wed, 1 Feb 2006 15:02:10 -0000
- From: "Andrey Kaliazin" <A.Kaliazin@xxxxxxxxxxx>
- Subject: Re: [Condor-users] Environment problems in submit files
Thanks Dan.
Great news!
btw, is there any easy way to specify in the submit file which
Condor version is required for a job to run?
I know there is CondorVersion variable with content something like
"$CondorVersion: 6.7.12 Sep 24 2005 $"
but it is really cumbersome and to match against.
Wouldn't it be better to introduce separate variables, like
Condor_major = 6.7
Condor_minor = 12
Then you would be able to add to requirements something like
(Condor_minor>14)
cheers,
Andrey
> -----Original Message-----
> From: condor-users-bounces@xxxxxxxxxxx
> [mailto:condor-users-bounces@xxxxxxxxxxx] On Behalf Of Dan Bradley
> Sent: Wednesday, February 01, 2006 1:40 PM
> To: Condor-Users Mail List
> Subject: Re: [Condor-users] Environment problems in submit files
>
> Andrey,
>
> I am embarrassed to have delayed the fix I promised you in
> 6.7.9 until
> now. The 6.7.15 release contains a full solution to the problem of
> specifying environment values when doing cross-platform submission
> (e.g. you can submit from unix to windows and still have
> semicolons in
> your 'path' environment value). The new syntax is platform
> independent
> and the delimiters (spaces) may be quoted, so you can still
> insert them
> into environment values if you need to.
>
> --Dan
>
> On Jun 17, 2005, at 9:31 AM, Dan Bradley wrote:
>
> >
> >
> > Andrey Kaliazin wrote:
> >
> >> Thanks Dan,
> >>
> >> I guess I have to go back to 6.6.9 and wait until those
> changes make
> >> way
> >> into release. Will it be 6.7.9 or the next one?
> >>
> >
> > Even if the full solution is not available, I will make
> sure there is
> > at least a workaround solution for 6.7.9.
> >
> >> Am I right to assume that the upcoming 6.6.10 will keep
> the old style
> >> behaviour in this case?
> >>
> > Yes.
> >
> > --Dan
> >
> >>> -----Original Message-----
> >>> From: condor-users-bounces@xxxxxxxxxxx
> >>> [mailto:condor-users-bounces@xxxxxxxxxxx] On Behalf Of Dan Bradley
> >>> Sent: Thursday, June 16, 2005 11:11 PM
> >>> To: Condor-Users Mail List
> >>> Subject: Re: [Condor-users] Environment problems in submit files
> >>>
> >>> Andrey,
> >>>
> >>> There was a change in behavior between 6.6.x and 6.7.x
> with respect
> >>> to environment settings when submitting between unix and
> windows.
> >>> Basically, you always use the delimiter that is
> appropriate for the
> >>> _submit_ node and Condor takes care of translating this to the
> >>> appropriate syntax for the execute node when the job
> description is
> >>> sent there. As part of the change, there was supposed to be
> >>> introduced a mechanism for escaping delimiters, but this has not
> >>> made it into a release yet. It was an oversight on my
> part to let
> >>> the one change be released without providing the other
> capability.
> >>> Sorry about that.
> >>>
> >>> In the mean time, you might be able to take advantage of a new
> >>> feature in 6.7.x (on the execute-node side) that allows you to
> >>> configure the runtime environment of the job.
> >>>
> >>>
> http://www.cs.wisc.edu/condor/manual/v6.7/3_3Configuration.html#10674
> >>>
> >>> For example, you should be able to configure it like this in the
> >>> config file that is read by your windows execute machines:
> >>>
> >>> STARTER_JOB_ENVIRONMENT =
> >>> path=c:\cygwin\bin;c:\windows;c:\windows\system32
> >>>
> >>> --Dan
> >>>
> >>> Andrey Kaliazin wrote:
> >>>
> >>>
> >>>> Dear all,
> >>>>
> >>>> We are using Windows XP computing farm with the Linux server and
> >>>> some users also find it convenient to submit windows binaries
> >>>>
> >>>> from the Linux box. And it used to work just fine until the
> >>> Linux submit box
> >>>
> >>>> was upgraded from 6.6.8 to 6.7.7 version.
> >>>> The problem emerged that the following line in submit file -
> >>> very convenient
> >>>
> >>>> way to set up the job environment -
> >>>> environment = path=c:\cygwin\bin;c:\windows;c:\windows\system32
> >>>>
> >>>> - is no longer accepted. The semicolon (;) is treated as a field
> >>>> separator character and is not escapable in any standard way I
> >>>> tried.
> >>>>
> >>>> In the manual it is said indeed, that the (;) is a field
> separator
> >>>> when submitting from UNIX boxes, while windows compute
> nodes require
> >>>> semicolon as a path separator.
> >>>>
> >>>> Is there any way to insert character (;) into
> environment variable
> >>>> or to tell condor_submit which character to use as a field
> >>> separator instead
> >>>
> >>>> of
> >>>> semicolon?
> >>>>
> >>>> regards
> >>>>
> >>>> Andrey Kaliazin
> >>>>
> >>>> _______________________________________________
> >>>> Condor-users mailing list
> >>>> Condor-users@xxxxxxxxxxx
> >>>> https://lists.cs.wisc.edu/mailman/listinfo/condor-users
> >>>>
> >>>>
> >>> _______________________________________________
> >>> Condor-users mailing list
> >>> Condor-users@xxxxxxxxxxx
> >>> https://lists.cs.wisc.edu/mailman/listinfo/condor-users
> >>>
> >>>
> >>
> >> _______________________________________________
> >> Condor-users mailing list
> >> Condor-users@xxxxxxxxxxx
> >> https://lists.cs.wisc.edu/mailman/listinfo/condor-users
> >>
> >
>
> _______________________________________________
> Condor-users mailing list
> Condor-users@xxxxxxxxxxx
> https://lists.cs.wisc.edu/mailman/listinfo/condor-users
>