Condor is a specialized workload management system for compute-intensive jobs. Like other full-featured batch systems, Condor provides a job queueing mechanism, scheduling policy, priority scheme, resource monitoring, and resource management. Users submit their serial or parallel jobs to Condor, Condor places them into a queue, chooses when and where to run the jobs based upon a policy, carefully monitors their progress, and ultimately informs the user upon completion.While providing functionality similar to that of a more traditional batch queueing system, Condor\'s novel architecture allows it to succeed in areas where traditional scheduling systems fail. Condor can be used to manage a cluster of dedicated compute nodes (such as a \"Beowulf\" cluster). In addition, unique mechanisms enable Condor to effectively harness wasted CPU power from otherwise idle desktop workstations. For instance, Condor can be configured to only use desktop machines where the keyboard and mouse are idle. Should Condor detect that a machine is no longer available (such as a key press detected), in many circumstances Condor is able to transparently produce a checkpoint and migrate a job to a different machine which would otherwise be idle. Condor does not require a shared file system across machines - if no shared file system is available, Condor can transfer the job\'s data files on behalf of the user, or Condor may be able to transparently redirect all the job\'s I/O requests back to the submit machine. As a result, Condor can be used to seamlessly combine all of an organization\'s computational power into one resource. Condor monitors a pool of machines to find idle machines that are then used to complete submitted jobs, and also provides remote system and checkpointing mechanisms that allow for transparent remote execution and job migration.NOTE: Condor is licensed and distributed under The Apache License.What\'s New in This Release: [ read full changelog ]New Features:· Condor now has a clipped port to i386 Debian 5.0 (Lenny).· Added standard universe support for gfortran.· Added support for standard output and standard error to be greater than 2 Gigabytes.Configuration Variable Additions and Changes:· The configuration variable JAVA_MAXHEAP_ARGUMENT now defaults to the value -Xmx1024m. The installation process of Condor resets this value to UNDEFINED in the local configuration file, if the detected JVM is not from Sun Microsystems.· A new feature has been added to the condor_master that makes it possible to append to the DC_DAEMON_LIST configuration variable, instead of overwriting it. To take advantage of this, place the plus character (\'+\') as the first character in the DC_DAEMON_LIST definition.· The new configuration variable DAGMAN_COPY_TO_SPOOL controls whether the condor_dagman binary gets copied to the spool directory when a DAG is submitted. See 3.3.25 for details.· Added -version and -help command line options to condor_submit_dag.Bugs Fixed:· Fixed a bug in the condor_collector which could cause it to hang indefinitely while reading network input in rare conditions.· Fixed a bug in condor_chirp for Windows which was causing it to crash on invocation.· Fixed a bug in the Windows condor_mail program, which was causing it to become unresponsive when run. If left running, the application also increased its memory consumption.· Fixed a bug that could cause the condor_schedd to never evaluate periodic expressions.· Fixed a bug on Unix platforms where condor_configure would provide incorrect defaults for the JAVA_MAXHEAP_ARGUMENT attribute in the installed configuration files. The new current default for Sun Java JVMs is -Xmx1024m.· Fixed a bug on Unix platforms where condor_configure would imply that using the Unix user root or UID 0 for the -owner option is a good thing. It is not, and would then complain that it could not find user root in the password file.· Fixed a bug on Unix platforms where condor_configure would emit errors about not being able to execute ldd when installing Condor on the Mac OS X 10.5 platform. condor_configure now correctly detects shared library requirements when installing the Condor binaries on the Mac OS X 10.5 platform.· Fixed a bug where execute-side daemons started before the condor_credd would fail to match with Windows jobs with run_as_owner set. This condition persisted until the execute-side daemons were either restarted or reconfigured.· Fixed a problem affecting the Job Router and Condor-C. When jobs spool input files, they enter a temporary hold state, which could trigger actions by a naive periodic remove or release expression. Periodic expressions are no longer evaluated when in this temporary hold state, which has the hold reason \"Spooling input data files\".· The example init script condor.boot.generic erroneously claimed that the condor_master would begin sending SIGKILL to child processes after 20 seconds if SIGQUIT (the fast shutdown) failed. The condor_master will actually wait $(SHUTDOWN_FAST_TIMEOUT) seconds, a value that currently defaults to 300 seconds.· Environment variable names are now properly treated as case-insensitive on Windows. The most common symptom of this bug was the inability to specify a custom PATH environment variable for a job from its submit description file.· Changed condor_submit -debug to issue a warning when ignoring environment variables. This occurs with getenv = True set in a submit description file.· Fixed a long-standing memory leak in SOAP interface. This caused the leak of a few hundred bytes of memory for each connection. This could eventually have caused the condor_schedd daemon to crash.· Fixed Job Router hooks so that their output is properly propagated where appropriate.· Implemented a fix for the condor_startd that prevents it from crashing if the user specified the configuration variable NUM_SLOTS_TYPE_N, without also specifying SLOT_TYPE_N.· The sample configuration files now correctly set the default universe to vanilla. This default has been true since 7.2.0, but was not reflected in the sample configuration files.· Fixed a bug that incorrectly set the value of the job ClassAd attribute RequestMemory to be 1024 times its correct size due to a mismatch in units; the attribute RequestMemory is given in Mbytes, while the attribute ImageSize is given in Kbytes.· Fixed a memory leak in condor_dagman that leaked a small amount of memory for each job submitted.· Fixed a bug that was causing the network mask to be advertised as a Condor sinful string, rather than a dotted-quad.· Fixed a handle leak in the condor_procd on Windows.Additions and Changes to the Manual:· Added a FAQ entry for Windows describing how machines with miss-configured performance counters may cause the condor_procd to crash.· Added a manual page for the command condor_router_history.