Fwd: AccessGrid/bin RunMe.py,1.1,1.2

[Robert Olson]

Ahem.

These processes are getting started asynchronously. I did not see the 
problem every time with the other ordering of the lines; I posit that we 
will not see the problem every time with this ordering of the lines either; 
I also posit that it will not work correctly every time.

The real solution involves adding the proper interlocking so that the 
process that is dependent on the other running first either waits to start 
until the other is going, or that it probes more than once for the service 
that it believes should be running.

Please also recall that the bugzilla archive is a public record. I do not 
find the comment there regarding this bug to be at all appropriate.

>From: "Ivan R. Judson" <judson at mcs.anl.gov>
>Date: Wed, 12 Mar 2003 02:09:45 -0600
>To: ag-cvs at mcs.anl.gov
>Subject: AccessGrid/bin RunMe.py,1.1,1.2
>Sender: owner-ag-cvs at mcs.anl.gov
>X-Spam-Status: No, hits=0.5 required=5.0 tests=X_NOT_PRESENT version=2.21
>X-Spam-Level:
>X-Whitelist-by-bob: yes
>
>Update of /cvsroot/AccessGrid/bin
>In directory pachelbel.mcs.anl.gov:/tmp/cvs-serv22007
>
>Modified Files:
>         RunMe.py
>Log Message:
>Fixed bug #125, it took switching two lines, big woop.