or the degree of difficulty removing them if I need to terminate the testing early Removing scheduled jobs is as easy as calling at -l and after some perlish manipulation of its output feeding it to at -r
CountZero A program should be light and agile, its subroutines connected like a string of pearls. The spirit and intent of the program should be retained throughout. There should be neither too little or too much, neither needless loops nor useless variables, neither lack of structure nor overwhelming rigidity." - The Tao of Programming, 4.1 - Geoffrey James
| [reply] [d/l] [select] |
I confess I do not know if there is a hard limit on the number of at-jobs, but that is easily circumvented, e.g. by splitting your huge list of at-jobs into separate batch-files and then having a master batch at-job file which calls (at appropriate times) the sub-at-job-batch files.
CountZero A program should be light and agile, its subroutines connected like a string of pearls. The spirit and intent of the program should be retained throughout. There should be neither too little or too much, neither needless loops nor useless variables, neither lack of structure nor overwhelming rigidity." - The Tao of Programming, 4.1 - Geoffrey James
| [reply] [d/l] [select] |