Our local Condor pool is maintained by the Condor Team, not the CSL. Please send all Condor-related requests to condor-admin@cs.wisc.edu. Condor utilities are installed in /unsup/condor/bin.
We encourage you to read about the policies currently in effect for our pool. When setting these policies, we strive to run jobs efficiently while minimizing the impact Condor makes on workstation owners. Please contact us with comments about our policies, especially if you believe that Condor is not effectively enforcing the policies. Please also contact us if you would like to customize the Condor configuration of your workstation.
The Condor Manual contains an overview of the Condor system and instructions for submitting jobs to Condor.
There is a mailing list for announcements about the UWCS Condor Pool. The Condor Team will try and give as much notice to this list as possible when we update the version of Condor installed on the pool or take downtime on critical machines. It will be an announcements-only, low-volume (1-2 messages a week on a very busy week) list. We would encourage all existing pool users to subscribe. To subscribe, please go to the mailing list signup page.
You will then need to respond to the confirmation email. Simply replying will be enough for most mail clients.
As always, the Condor pool is maintained by the Condor Team, and our preferred contact email address is condor-admin@cs.wisc.edu Please do not send Condor issues to lab@cs.wisc.edu.
When you compile on CentOS 4.5, you should use the GCC 3.2.2 family of compilers found in /s/gcc-3.2.2/i386_cent40/bin/:
Note that your entire program must be compiled with the 3.2.2 compilers, not just linked with them.
Condor runs without AFS credentials, so you must grant net:cs access to all Condor job input, output, and log files stored in AFS directories. (To find if a directory is in AFS, run pwd in that directory. If the output of the pwd command begins with /afs, the directory is on AFS and these instructions apply.) To do this, run "fs setacl path net:cs read" or "fs setacl path net:cs write" for each directory path accessed by your Condor jobs. For more information about AFS, please consult the CSL FAQ (search the page for "AFS").
Instead of using AFS you can keep your files on local disk (typically /scratch) and use Condor's file transfer mechanism. See the manual for more details.
The UW Madison CS Condor pool has been configured to check for a MemoryRequirements parameter in all Condor jobs. This parameter specifies, in megabytes, how much physical memory your job needs to run efficiently. If this parameter is not specified, Condor will assume a default value of 128 MB. Condor will only run jobs on machines with enough available physical memory to satisfy the jobs' memory requirements.
To specify this parameter, please add the following to your job description file(s):
+MemoryRequirements = 90replacing 90 with the actual memory requirements of your job in megabytes.
We encourage you to continue to specify your job's virtual memory requirements with the image_size command in your job description file.
CondorView presents summary statistics of our local Condor pool's utilization via the Web. The data for these visualizations is derived from Condor's own accounting statistics.
We encourage you to read about the policies currently in effect for our pool.