Re: [Condor-users] condor_run question

[Matthew Farrellee <matt@xxxxxxxxxx>]

$ man condor_run

...

$ CONDOR_REQUIREMENTS=OHMY condor_run sleep 10

(at another prompt)
$ condor_q -long | grep ^Requirements
Requirements = (OHMY) && (Arch == "INTEL") && (OpSys == "LINUX") && (Disk >= DiskUsage) && ((Memory * 1024) >= ImageSize) && (TARGET.FileSystemDomain == MY.FileSystemDomain)

Now if you're on Windows you can probably do the sensible thing there.

Best,


matt

Mag Gam wrote:
> can anyone help us out with this?
> 
> 
> 
> On Thu, Oct 1, 2009 at 7:57 PM, Mag Gam <magawake@xxxxxxxxx> wrote:
>> I am trying to figure out how I create the CONDOR_REQUIREMENTS env variable.
>>
>> Does anyone have a sample of this variable? Currently, when I run
>> condor_run "command" the job is in idle because of requirements. I
>> then do:
>>
>> condor_qedit
>>
>> condor_reschedule and it works
>>
>> But what is the correct way to set the CONDOR_REQUIREMENTS variable,
>> an example would be very helpful!!!
>>
>> TIA
>>
>> On Thu, Oct 1, 2009 at 9:05 AM, Mag Gam <magawake@xxxxxxxxx> wrote:
>>> I am trying to use condor_run to execute simple scripts with pipes and
>>> its complaining about requirements. I know there is an env variable to
>>> set for requirements but its still not working. It has to do something
>>> with paranteses ().
>>>
>>> I am using condor_history -l jobid to get my requirements of previous
>>> jobs but how can I use those requirements with condor_run ?
>>>
>>> Does anyone have any examples of previously executed job's
>>> requirements and condor_run requirements?
>>>
>>>
>>> TIA
>>>
> _______________________________________________
> Condor-users mailing list
> To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with a
> subject: Unsubscribe
> You can also unsubscribe by visiting
> https://lists.cs.wisc.edu/mailman/listinfo/condor-users
> 
> The archives can be found at: 
> https://lists.cs.wisc.edu/archive/condor-users/