Mailing List Archives
Authenticated access
|
|
|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Condor-users] configure condor with environment vaiables
- Date: Mon, 14 May 2012 12:44:45 +0100
- From: Hao Liu <hao.liu@xxxxxxxxxxxxxx>
- Subject: Re: [Condor-users] configure condor with environment vaiables
Yes, that is the problem! Thanks to you all.
Regards,
Hao
On 14 May 2012, at 11:42, Matthew Farrellee wrote:
> You should check your environment and make sure the escaping was correct.
>
> $ export _CONDOR_START=Owner=="xxx"||Owner=="yyy"
> 06:33:38am> eeyore:~/Documents/CondorInstallation $ echo $_CONDOR_START
> Owner==xxx
> $ export _CONDOR_START='((Owner == "xxx") || (Owner == "yyy"))'
> $ echo $_CONDOR_START
> ((Owner == "xxx") || (Owner == "yyy"))
>
> export with the ''s works for me in my shell.
>
> You should also figure out why the environment was used to configure condor and evaluate if it is still necessary.
>
> Best,
>
>
> matt
>
> On 05/14/2012 06:19 AM, Hao Liu wrote:
>> Hi Matt,
>>
>> Thanks for the explanation. However,
>> export _condor_START=((Owner=="xxx")||(Owner=="yyy")) did Not work, still have the error of "required attribute START is not defined".
>> I also tested export _condor_START=Owner=="xxx"||Owner=="yyy" (note with brackets removed), it could start the daemon, but it did not accept any jobs either from xxx or yyy.
>>
>> The only two worked fine until now are:
>> export _condor_START=true
>> export _condor_START_owner="xxx"
>>
>> Any idea? Thanks.
>>
>> Hao
>>
>>
>>
>> On 13 May 2012, at 22:18, Matthew Farrellee wrote:
>>
>>> On 05/13/2012 11:03 AM, Hao Liu wrote:
>>>> Hi,
>>>>
>>>> My predecessor configured condor by using environment variables, such as
>>>> export _condor_START_owner=${USER}.
>>>> I understand this is to config START expression with owner attribute.
>>>> But how does this work?
>>>>
>>>> This is only ref I found: "Some Condor tools utilize environment
>>>> variables to set their configuration. These tools search for
>>>> specifically-named environment variables. The variables are prefixed by
>>>> the string_CONDOR_or _condor_. The tools strip off the prefix, and
>>>> utilize what remains as configuration."
>>>>
>>>> Following the format I made some change, but some worked some did not work:
>>>>
>>>> export _condor_START=true (work, allow any one to run jobs)
>>>> export _condor_START=((Owner="xxx")||(Owner="yyy")) - doesn't work,
>>>> error "Required attribute "START" is not defined"
>>>> export _condor_START_owner="xxx"||"yyy" - "Required attribute "START" is
>>>> not defined"
>>>>
>>>> so how to configure condor by environment variables, this prefix suffix way?
>>>>
>>>> Thanks,
>>>> Hao
>>>
>>> Wow, that's a gem. START_owner is a param just as START is. START_owner should probably fade into history, if it hasn't already.
>>>
>>> 'START_owner = ""xyz""' will generate 'START = Owner == "xyz"', or in your case 'START = Owner == ""xxx"|"yyy""', which has no hope of working. I recommend purging START_owner from your memory.
>>>
>>> That illustrated the problem though,
>>>
>>> export _condor_START=((Owner=="xxx")||(Owner=="yyy"))
>>>
>>> should work. Given the appropriate shell escaping. Note == vs =.
>>>
>>> You are correct in thinking "_condor_" is the prefix Condor will use to pick up configuration from the environment.
>>>
>>> Best,
>>>
>>>
>>> matt
>>
>