Recent changes have been made such that Condor doesn't necessarily create a local spool dir unless explicitly configured. http://condor-wiki.cs.wisc.edu/index.cgi/chngview?cn=16085 Some of the packaged scripts such as sshd.sh and lamscript (MPI wrapper) rely on a non-null value of _CONDOR_REMOTE_SPOOL_DIR. We need to address this in documentation or changes to the affected scripts so that there is no assumption that the spool directory is present. ./condor_scripts/lamscript:_CONDOR_REMOTE_SPOOL_DIR=$_CONDOR_REMOTE_SPOOL_DIR ./condor_scripts/sshd.sh:_CONDOR_REMOTE_SPOOL_DIR=$_CONDOR_REMOTE_SPOOL_DIR ./condor_scripts/sshd.sh:$CONDOR_CHIRP put -perm 0700 $idkey $_CONDOR_REMOTE_SPOOL_DIR/$_CONDOR_PROCNO.key ./condor_scripts/sshd.sh: $CONDOR_CHIRP put -mode cwa - $_CONDOR_REMOTE_SPOOL_DIR/contact ./condor_scripts/sshd.sh: $CONDOR_CHIRP fetch $_CONDOR_REMOTE_SPOOL_DIR/contact $_CONDOR_SCRATCH_DIR/contact ./condor_scripts/sshd.sh: $CONDOR_CHIRP fetch $_CONDOR_REMOTE_SPOOL_DIR/$node.key $_CONDOR_SCRATCH_DIR/tmp/$node.key ./condor_scripts/sshd.sh: $CONDOR_CHIRP remove $_CONDOR_REMOTE_SPOOL_DIR/$node.key ./condor_scripts/sshd.sh: $CONDOR_CHIRP remove $_CONDOR_REMOTE_SPOOL_DIR/contact
We could create a spool dir by checking for WANT_REMOTE_IO in the submit. However, it's unclear we even need the SPOOL dir for things like sshd.sh (/tmp anyone?)
*** This bug has been marked as a duplicate of bug 549432 ***