Feature #4926
Add self-destruct timer option for wrapper scripts
Start date:
11/08/2013
Due date:
% Done:
0%
Estimated time:
Stakeholders:
Description
Sometimes you need to debug why a job is hanging, and you get no logs if you just condor_rm the job.
If the wrapper script can be set to self-destruct after a timeout, you at least get logs back.
History
#1 Updated by Parag Mhashilkar almost 7 years ago
- Assignee set to Dennis Box
#2 Updated by Parag Mhashilkar almost 7 years ago
- Category set to JobSub Tools
#3 Updated by Dennis Box about 6 years ago
- Description updated (diff)
- Status changed from New to Assigned
#4 Updated by Dennis Box over 5 years ago
- Target version set to v1.1.9
#5 Updated by Dennis Box over 5 years ago
- Status changed from Assigned to Feedback
- Assignee changed from Dennis Box to Parag Mhashilkar
*see branch 4926
- add --timeout setting to kill jobs if they run longer than specified
- some reformatting to look better with --help
- some reformatting as suggested by pylint
- found an indentation error from #10493 which resulted in unnecessary log messages when no -d specified
#6 Updated by Dennis Box about 5 years ago
- Status changed from Feedback to Closed