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!
- -_condor_cmd_fd - File descriptor that the caller will stream a command file in on. Used by the starter.
- -_condor_cmd_file <filename> - File to read the command file from. Not used, but may be useful for debugging.
- -_condor_debug_wait - Upon starting up, the process will enter an infinite loop, allowing you to attach to a debugger where you can break the loop.
- -_condor_nowarn - Disable notice messages. Obsolete, prefer "-_condor_warning UNSUP OFF"
- -_condor_warning <kind> <mode> - Set warning level.
- <kind> can be: ALL, NOTICE, READWRITE, UNSUP, BADURL
- <mode> can be: ON, OFF, ONCE
- -_condor_D_<LEVEL> - Add D_<LEVEL> to the debug levels being logged. eg "-_condor_D_FULLDEBUG" turns on D_FULLDEBUG.
- -_condor_ckpt <filename> - File to checkpoint into.
- -_condor_restart <filename> - Restart from the checkpoint <filename>. Implies "-_condor_ckpt <filename>". For safety and clarity, specify -_condor_ckpt or -_condor_retart, not both. If you specify both, the <filename> specified in the last one will be used for both.
- *-_condor_
Attachments:
- checkpoint-wrapper
4994 bytes added by adesmet on 2012-Jul-25 15:22:40 UTC.
Perl implementation of wrapper implementing Condor Syscall library checkpointing in the vanilla universe.
