6.3 Macintosh OS X

This section provides information specific to the Macintosh OS X port of Condor. The Macintosh port of Condor is more accurately a port of Condor to Darwin, the BSD core of OS X. Condor uses the Carbon library only to detect keyboard activity, and it does not use Cocoa at all. Condor on the Macintosh is a relatively new port, and it is not yet well-integrated into the Macintosh environment.

Condor on the Macintosh has a few shortcomings:

• Users connected to the Macintosh via ssh are not noticed for console activity.
• The memory size of threaded programs is reported incorrectly.
• No Macintosh-based installer is provided.
• The example start up scripts do not follow Macintosh conventions.
• Kerberos is not supported.

6.3.1 Macintosh OS X Panther (10.3)

Condor Version 6.8.3 is built on a machine running Panther (10.3). Therefore, these binaries work on any PPC machine running MacOS 10.3.

6.3.2 Macintosh OS X Tiger (10.4)

Even though Condor Version 6.8.3 is built on a machine running Panther (10.3), the resulting binaries are known to work on PPC machines running MacOS 10.4.

6.3.3 Macintosh OS X Tiger (10.4) for Intel CPUs

Condor does not yet provide Universal binaries or natively-built binaries for Intel MacOS 10.4. Given MacOS's support for running PPC binaries in emulation (their ``Rosetta'' system), the existing Condor binaries built for PPC MacOS 10.3 might work. Very few parts of the Condor system are performance bottle-necks, so running in emulation will hopefully cause no problems. The end-user applications (the jobs submitted to Condor), should probably be Universal binaries or x86-specific, to provide the most throughput on these machines.