My bad - the background job is actually running - I just needed to use absolute paths. Sorry for confusion.
On Tuesday, 5 January 2016 11:51:33 UTC, Tomasz Kuchta wrote: > > Hi All, > I have an async command that is invoking a Bash script. > The script invokes some other scripts in background (using "&"). > I have noticed that the background command is either not called or it > terminates immediately (not sure). > The same script works in non-asynchronous mode (using the shell module) - > the background jobs are controlled, > so I would terminate them before the script finishes. > It seems to me that this might have something to do with the fact that > async tasks are run differently. > Is is an expected behaviour or I should be able to run background tasks > like this? > > Thanks! > -- 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/46056fd5-8545-47f6-a507-e43dbef7f23d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
