[Pipet Devel] dl2bl file not written
J.W. Bizzaro
jeff at bioinformatics.org
Wed Feb 28 06:27:23 EST 2001
Jarl van Katwijk wrote:
>
> I think the problem is that ./runpiper executes the BL too soon after
> the PL is still booting up. If you know how to build in a delay before
> the execution of the BL the problem is probably gone. Could you check
> this out, I tried to find the Python code for a delay, but couldn't find
> any.
For a better, permanent solution, can we at some point have the PL (or each
layer) "say" that they are ready? Can we have the PL place its PID in a file
somewhere?
I just think that an arbitrary delay might not always work. What if the PL is
on a slower computer and requires more time than N seconds? And, on faster
computers the PL might start much quicker than N seconds.
Jeff
--
J.W. Bizzaro jeff at bioinformatics.org
Director, Bioinformatics.org: The Open Lab http://bioinformatics.org/~jeff
"All those scientists--they're all alike! They say they're working for us,
but what they really want is to rule the world!"
-- Angry Villager, Young Frankenstein
--
More information about the Pipet-Devel
mailing list