8.7 Stable Release Series 6.4

This is the stable release series of Condor. New features will be added and tested in the 6.5 development series. The details of each version are described below.

Version 6.4.8

New Features:

• None.

Bugs Fixed:

• The starter would crash if the execute directory contained symlinks from child to parent directories.

• condor_submit_dag allowed you to submit a DAG which contained jobs with no log file (as long as ALL jobs had no logfile)

• Dagman would RETRY your jobs as specified, but did properly note that the failed job was no longer in the queue. The result is that Dagman thought there were more jobs yet to finish when in fact all had actually finished, which caused it exit with failure.

Known Bugs:

• None.

Version 6.4.7

New Features:

• . None

Bugs Fixed:

• Fixed major problem with inflated job counts in condor_ status -submitter
• Fixed a problem with the UserLog parser if the Aborted, Held, or Removed event did not have the optional reason string that caused those events to be ignored.

• Fixed a problem with Condor-G on some older Linux distributions that would cause it to crash on startup because of an invalid file descriptor for stderr

Known Bugs:

• None.

Version 6.4.6

New Features:

• Clarified the output of condor_ q -analyze.

Bugs Fixed:

• Fixed a major bug that caused standard universe Condor jobs to crash whenever they ran in a pool with the LOWPORT and HIGHPORT config file settings enabled. These settings restrict what ports Condor will use in your pool. To allow standard universe jobs to run in such a pool, you must relink your executable with condor_ compile after the 6.4.6 condor libraries are installed in your Condor lib directory.

• When more than 512 distinct users submit to Condor or Condor-G, the condor_ schedd no longer crashes.

• DAGMan now correctly reports an error and rejects DAGs which contain two nodes with the same name; in the past DAGMan did not detect this, and would not exit even when the DAG was complete.

• DAGMan now correctly reports an error when the null string is passed to any of its arguments which require a filename.

• The -format option to condor_ q and condor_ status can now be used to print out boolean expressions in ClassAds, not just strings, integers and floating point numbers. Any boolean expression will now be treated like a string, so be sure to use %s as the conversion character in the formatting string you pass to -format.

• If no Rank is specified in the job description file, or in the DEFAULT_RANK config file variable, the default value is now ``0.0'' not just ``0''. Since Rank is supposed to be a floating point value, the ``0.0'' ensures that the -format option to tools like condor_ q and condor_ status will always treat this variable as a float.

• Fixed the help message for the condor_ rm, condor_ hold and condor_ release tools to be more helpful, and to mention the -constraint option.

• When you ran condor_ q in a way that it needed to query the condor_ collector and that query failed, the error message used to be very short and cryptic. Now, there is a verbose message that explains what went wrong and possible ways you can fix the problem. Also fixed a misleading error message in condor_ q that was displayed under very rare circumstances.

Packaging Changes:

• Begining with Condor version 6.4.6, all of the Condor-G related binaries (condor_ gridmanager, condor_ glidein, and gahp_server) are also included in the full release of Condor. So, if you are using the full Condor system and want to use Condor's grid-enabled functionality, you no longer need to download and install a separate ``contrib module''. However, if all you want is Condor-G, the contrib module is still available. For more information, please the chapter on ``Grid Computing'' on page .

• Fixed a process family managment bug in the condor_ startd on Windows. This bug was preventing the condor_ startd from detecting the condor_ starter as a member of its process family.

Version 6.4.3

New Features:

• Added a -hold and -held option to condor_ q which displays the reason that the job had been held.

Bugs Fixed:

• Fixed a bug where more than one space between arguments to a job in the java universe would result in it being invoked with and incorrect list arguments.

• Removed renaming of the executable to condor_exec in the java universe. This fixes a bug where the JVM was looking at its path to determine its installation directory.

• Fixed a bug and resulting null pointer exception in the java universe because under certain conditions, Condor would invoke the JVM incorrectly.

• Fixed serveral error reporting messages to be more precise.

• When the NIS environment was being used, the condor_ starter daemon would produce heavy amounts of NIS traffic. This has been fixed.

• Binary characters in the StarterLog file and a possible segmentation fault have been fixed.

• Fixed select(2) in the standard universe on our Linux ports.

• Fixed a small bug in condor_ q that was displaying the wrong username for ``niceuser'' jobs.

• Fixed a bug where, in the standard universe, you could not open a file whose name had spaces in it.

• Fixed a bug in DAGMan where pre and post scripts would fail to run if the DAG description file had extra whitespace. Also, reworded the error messages DAGMan produces when it fails to parse the DAG description file to be more clear and helpful for solving the problem.

• Fixed some misleading error messages in the Condor log files when there were permission problems trying to execute a program.

• Condor for Windows will now run on Windows XP.

• Condor for Windows now supports the Java Universe.

• Users logged into Windows Domain accounts rather than local accounts can submit jobs.

• Potential Windows registry bloating bug fixed. Condor for Windows no longer creates and deletes an account on the execute machine each time a job is run. Instead, a single account for each VM on the execute machine is created once and enabled or disabled as needed.

• Cross-submits from Windows to Unix and from Unix to Windows are now supported, provided that both platforms are running Condor 6.4 series daemons.

• Free disk space is now reported accurately on Windows.

• A rare but serious bug that could allow non-Condor processes to be added to the Condor process family on Windows has been fixed.

• Condor for Windows will now also run 16-bit applications.

• Fixed a minor bug where certain integer attributes in the condor_config file might not have been properly parsed if they were defined in terms of other config file attributes, using the $(attribute) notation.

Known Bugs:

• You may not open a file in the standard universe whose name contains a colon ``:''.

Version 6.4.2

New Features:

• . This release mirrored the Condor-G release, and has no new features.

Bugs Fixed:

• None.

Known Bugs:

• None.

Version 6.4.1

New Features:

• None.

Bugs Fixed:

• Users are now allowed to answer ``none'' when prompted by the installer to provide a Java JVM path. This avoids an endless loop and leaves the Java abilities of Condor unconfigured.

Known Bugs:

• None.

Version 6.4.0

New Features:

• If a job universe is not specified in a submit description file, condor_ submit will check the config file for DEFAULT_UNIVERSE instead of always choosing the standard universe.

• The D_SECONDS debug flag is deprecated. Seconds are now always included in logfiles.

• For each daemon listed in DAEMON_LIST, you can now control the environment variables of the daemon with a config file setting of the form DAEMONNAME_ENVIRONMENT, where DAEMONNAME is the name of a daemon listed in DAEMON_LIST. For more information, see section 3.3.9.

Bugs Fixed:

• Fixed a bug in the new starter where if the submit file set no arguments, the job would receive one argument of zero length.

Known Bugs:

• None.