Search Results

Thanks, fixed.

The trick is to save the next number after every success; otherwise, don't bother saving. Otherwise, you will be off-by-one...

Also, don't put anything but the program line in...

If you want to do it without a makefile:

#!/bin/sh

if [ "$#" -gt 0 ]
then
X="$1"
elif [ -f lastfile ]
then
read X < lastfile
fi

[ -z "$X" ] && X=1

R=1

while [...

That's what the 'touch' is for in the makefile, to create flag files on success to remember where it left off.

Here is an example, written on the assumption your programs create no files.

# Named Makefile, in the current directory
file4:file3
./sqr.ksh axpyi035_sf axpyi035_sf.par $1 $2 XHRPPYA4;...

You can use makefiles for anything. It is a list of what files are used to create what files, and what programs are used to create them. It can start in the middle, by seeing what files have...

What about output files? Is there a file it would create only if it succeeded? I was thinking of using a makefile.

What do these processes do? Do they create files you can use to tell where to continue?