The starter accepts incoming Chirp requests and converts them into remote I/O operations to the appropriate I/O device. This is currently the shadow process at the job submission site. However, it is entirely possible to re-route these to a nearby storage appliance such as a NeST.
-The starter provides security services for the job's I/O by communicating over CEDAR, the standard Condor socket abstraction. This layer provides a wide range of encryption and authentication methods, including Kerberos, GSI, and SSPI. The exact protocol used depends on a negotiation between the execution and storage sites. By tunneling I/O through the starter, the user is able to take advantage of secure I/O with a minimum of burden on the application.
+The starter provides security services for the job's I/O by communicating over CEDAR, the standard HTCondor socket abstraction. This layer provides a wide range of encryption and authentication methods, including Kerberos, GSI, and SSPI. The exact protocol used depends on a negotiation between the execution and storage sites. By tunneling I/O through the starter, the user is able to take advantage of secure I/O with a minimum of burden on the application.
{subsection: Implementation Status}
The I/O proxy server is checked into the new starter/shadow on V6_3-branch.
@@ -51,4 +51,4 @@
The Java support is coded up in the new starter/shadow. Pending some more testing, I will check it into the 6.3-branch.
{subsection: Compiling Notes}
-The C portion of the Java Universe is built automatically with the rest of Condor. However, two small Java programs are necessary to build a complete release. If HAS_JAVA=YES in site.def, then these programs will be built using the =JavaCompiler= variable and placed in release_dir/lib. If HAS_JAVA=NO, then the release will be built with all the Java support except the two small Java programs. The startd will operate correctly, but will not advertise or run Java without the two classes. If we don't care to install a javac on all of our development platforms, these two programs could be compiled on Linux, placed in a standard directory, and then simply copied into the distribution from any platform.
+The C portion of the Java Universe is built automatically with the rest of HTCondor. However, two small Java programs are necessary to build a complete release. If HAS_JAVA=YES in site.def, then these programs will be built using the =JavaCompiler= variable and placed in release_dir/lib. If HAS_JAVA=NO, then the release will be built with all the Java support except the two small Java programs. The startd will operate correctly, but will not advertise or run Java without the two classes. If we don't care to install a javac on all of our development platforms, these two programs could be compiled on Linux, placed in a standard directory, and then simply copied into the distribution from any platform.
