This is the same command line as before, but -_condor_ckpt is now -_condor_restart and -_condor_relocatable has been added. -{subsection: Checkpointing in Condor's vanilla universe} +{subsection: Checkpointing in HTCondor's vanilla universe} 1: Register a signal handler for SIGTERM; it should send SIGTSTP to the running "real" job. 1: Register a signal handler for SIGTSTP; it should send SIGTSTP to the running @@ -42,7 +42,7 @@ 2: Register a signal handler for SIGUSR2; it should send SIGUSR2 to the running "real" job. (As of July, 2012, this will never be used, but we anticipate adding support for periodic checkpoints in the vanilla universe.) 3: Is the checkpoint file ("my-real-job.ckpt") present? Then the arguments are "-_condor_restart my-real-job.ckpt -_condor_relocatable". Otherwise the arguments are "-_condor_ckpt my-real-job.ckpt". 3: Start your "real" job -*:: Start under setarch to disable address randomization and similar that Condor checkpointing cannot cope with. The "-B" (limiting memory to 32 bit addresses) may not be necessary in all cases, but the specific circumstances are not known. The _<arguments>_ are as determined above. +*:: Start under setarch to disable address randomization and similar that HTCondor checkpointing cannot cope with. The "-B" (limiting memory to 32 bit addresses) may not be necessary in all cases, but the specific circumstances are not known. The _<arguments>_ are as determined above. *::: 32-bit: setarch i386 -L -B -R ./my-real-job _<arguments>_ *::: 64-bit: setarch x86_64 -L -B -R ./my-real-job _<arguments>_ *:: Note the PID, for use in the signal handlers mentioned above. @@ -83,7 +83,7 @@ {section: Command line} -A program that has been condor_compiled takes additional command line options. Generally speaking end users shouldn't need to know this; Condor will invoke them automatically. But for testing or doing checkpointing without the standard universe, this might be useful. _These are officially undocumented and may change without warning!_ +A program that has been condor_compiled takes additional command line options. Generally speaking end users shouldn't need to know this; HTCondor will invoke them automatically. But for testing or doing checkpointing without the standard universe, this might be useful. _These are officially undocumented and may change without warning!_ *: *-_condor_cmd_fd <FD>* - File descriptor that the caller will stream a command file in on. Also enables remote syscalls. Used by the starter. Incompatible with -_condor_cmd_file. *: *-_condor_cmd_file <filename>* - Identical to -_condor_cmd_fd, except that the command file is read from <filename> instead of an FD. Incompatible with -_condor_cmd_fd.