Thanks. In the end, I found out that my target application has a setting
whereby the application becomes instantly detectable to the monitoring side
of my script. After doing this, the associated resource is created
flawlessly every time.
On Tue, Apr 16, 2019 at 1:46 PM Jan Pokorný wrote:
>
[letter-casing wise:
it's either "Pacemaker" or down-to-the-terminal "pacemaker"]
On 16/04/19 10:21 -0600, JCA wrote:
> 2. It would seem that what Pacemaker is doing is the following:
>a. Check out whether the app is running.
>b. If it is not, launch it.
>c. Check out again
>d.
Thanks to everybody who has contributed to this. Let me summarize things,
if it is only for my own benefit - I learn more quickly when I try to
explain that I am trying to learn something to others.
I instrumented my script in order to find out exactly how many times it is
invoked when creating
