Now that we can specify a location when invoking batch_start.php, there is an issue with our lock files. It would be possible to launch TWO or more runs from this single directory if each had a different location (since location/device is part of the lockfilename). The points of contention for multiple runs are: a) the status table (since we clear out the table each time we launch a run); b) the batch.log (since we delete this file each time we start a job). Both of these points are based on current directory, so starting now we put the lock files in the current directory and do NOT use the $device in the filename. (Later I need to go back and remove the $device param from the function & callers.)
Now that we can specify a location when invoking batch_start.php, there is an issue with our lock files. It would be possible to launch TWO or more runs from this single directory if each had a different location (since location/device is part of the lockfilename). The points of contention for multiple runs are: a) the status table (since we clear out the table each time we launch a run); b) the batch.log (since we delete this file each time we start a job). Both of these points are based on current directory, so starting now we put the lock files in the current directory and do NOT use the $device in the filename. (Later I need to go back and remove the $device param from the function & callers.)

git-svn-id: d5a8a4092b1c3eddbe100e0c5fc6446cfb12afd1@884 fc7d47d3-c008-acd5-f51f-d19787b8a02f

HTTPArchive/httparchive,HTTPArchive/httparchive,paulcalvano/httparchive,paulcalvano/httparchive