So a few things here. Having just breezed over what WebLogic Node Runner does, I see where something like service or supervisor is somewhat redundent for you. That wasn't clear to me from from this thread until I did that though. That's not the norm for most though and you weren't clear on that so I don't think its fair to say Brian is missing the point.
So I think I get what you are trying to do. We've been in a similar spot here with long running processes rather than daemons, but I think what we did applies here. Use the the wait_for directive right after your shell nohup async task and look for a sign that the initialization of the previous task has reached a ready state. What is "ready" will depend on you. In our case it's a specific line in a log file. Not ideal or elegant, but it should work. Now, based on what I read, it sounds like the elegant solution would be to create a noderunner module where you can better manage and control the jobs abstracted from your playbook or role. Hope that helps. -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/9e182cb7-e345-470e-9e93-6b12967b85b7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
