Search Results

With the status file it is harder to compute the next job.
Don's approach has it hard-coded, this is inflexible in case you want to add or remove a job(-script).
The following uses a status file...

It is most simple record the jobs to be skipped, i.e. the good jobs.
Then initially the "good" file can be empty or missing.
#!/bin/bash
good=./good
for job in script1.sh script2.sh script3.sh...