Hi
This is a problem i am also facing. It would appear that the command runs 
within a process group that is killed when ansible finishes the task. I have 
tried using nohup and & to run the command, whi choose works but because they 
are background processes i cannot tell if they are succesful. 

Another approach is async but i dont knkw how to ensure the command stays alive 
after the task has finished. 

This us a short fall that makes ansible a little harder to develop for as 
background tasks that under a normal shell default to root context are not in 
ansible.

I wish there a more supported way to make this work.

Nicholas Irving

-- 
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/c4454da4-7de1-4a0e-9d9e-7901ddad43eb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to