On Wed, Dec 30, 2015 at 3:40 AM, chris meyers <[email protected]> wrote:
> Please be more specific. What is nohup lacking that salt --async has that > you would like? > Ansible is interactive by nature, so it uses stdin. Using nohup will only work if the playbook runs very nicely. Any arising question (for example, accept an unknown ssh key) will stop the playbook. So I believe that one of the the ´async´ functionalities missing is handling playbook questions. If the use of nohup is just to capture both stdout & stderr, there are other ways to do it. Javier Palacios -- 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/CANsNpURt8dYkTys-mf%2By6DrJG%3DQ%2BrU%2B0EMRu6wTQ-d39s9gKzQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
