Condor-G Example 2 - Stage An Executable and Specify Inputs


In this exampl e we will submit a job that runs a user-supplied application that requires two command line arguments. Condor will need to transfer the application to the grid computer.

Build the application for correct architecture
Use of Static vs. Shared Libraries

Create a Condor submit file called example2.submit and which contains the following lines:

executable = myapp
arguments=  George 90
Transfer_Executable = true
globusscheduler = beowulf2.dartmouth.edu/jobmanager-fork
universe = globus
output = myapp.out
error=myapp.error
log = myapp.log
queue


Next check  the libraries required by the application, submit the job to Condor and wait for the job to complete


sierra:~> ldd myapp
libm.so.6 => /lib64/tls/libm.so.6 (0x0000002a95683000)
libc.so.6 => /lib64/tls/libc.so.6 (0x0000002a9580b000)
/lib64/ld-linux-x86-64.so.2 => /lib64/ld-linux-x86-64.so.2 (0x0000002a95556000)

sierra:~> condor_submit example2.submit
Submitting job(s).
Logging submit event(s).
1 job(s) submitted to cluster 12.
sierra:~> condor_q -globus

-- Submitter: sierra.dartmouth.edu : <129.170.16.93:32921> : sierra.dartmouth.edu
ID OWNER STATUS MANAGER HOST EXECUTABLE

12.0 sas SUBMITTED fork beowulf2.dartmouth /home/sas/myapp


sierra:~> condor_q -globus

-- Submitter: sierra.dartmouth.edu : <129.170.16.93:32921> : sierra.dartmouth.edu
ID OWNER STATUS MANAGER HOST EXECUTABLE

12.0 sas ACTIVE fork beowulf2.dartmouth /home/sas/myapp

sierra:~> condor_q -globus

-- Submitter: sierra.dartmouth.edu : <129.170.16.93:32921> : sierra.dartmouth.edu
ID OWNER STATUS MANAGER HOST EXECUTABLE

12.0 sas DONE fork beowulf2.dartmouth /home/sas/myapp

sierra:~> cat myapp.out
Hi George. The sine of 90 is 1














Previous Top Next


CondorG_Example2.src  last modified Jun 8, 2005 Introduction Table of Contents
(frame/no frame)
Printable
(single file)
© Dartmouth College