I tripped over my fingers yesterday and triggered another
slow srsbuild of genbank on my slow system. Then another
data update last night triggered srscheck/srsbuild which
started rebuilding genbank while the first build was in
progress. Is this a situation that can be avoided by,
for instance, creating "index/genbank.lock" files while one build
is in progress so that a new build of the same data will
not start?
Thanks, Don
--
-- d.gilbert--biocomputing--indiana u--bloomington--gilbertd at bio.indiana.edu