I am sorry but I am not familiar with that. Do you have a solution to this problem. Any relevant documentation?
On Friday, September 5, 2014 5:17:01 AM UTC-7, Philippe Eveque wrote: > > You mean acting as a remote wall(1) ? > > maybe then just pipe the output to wall(1) > > > Phil > > > > 2014-09-05 6:50 GMT+02:00 Imran Khan <[email protected] <javascript:>>: > >> --- >> >> - hosts: server >> gather_facts: False >> >> tasks: >> - name: Run runserver.sh and save the output of script >> shell: screen -dRR bash /home/dell/tester_server_2/runserver.sh >> async: 99999999999 >> poll: 0 >> >> I have already incorporated sth like that in my playbook. Now what I need >> is that if any of the remote nodes have been accessed by using Puttty or >> OpenStack Dashboard, they should display the output of the script on that >> individual screen. For instance, if the script I am executing contains *echo >> "hello from ansible control node" *and then goes to sleep for some time. >> The output on the individual user (all the nodes) should be *hello form >> ansible control node *. Each remote node should display this message on >> their respective screen, so that it is readable to any user that is >> currently *sshed* into the VM. >> >> >> >> >> >> On Thursday, September 4, 2014 6:25:18 PM UTC-7, Michael DeHaan wrote: >>> >>> See here for some info about running "fire and forget" non-blocking >>> tasks. >>> >>> http://docs.ansible.com/playbooks_async.html >>> >>> You may also be instead interested in >>> >>> http://docs.ansible.com/faq.html#how-do-i-keep-secret- >>> data-in-my-playbook >>> >>> Depending on how I interpret the question about "not seeing local >>> output", one or both may be appropriate. >>> >>> >>> >>> >>> On Thu, Sep 4, 2014 at 6:38 AM, Imran Khan <[email protected]> wrote: >>> >>>> >>>>> Maybe sth like: >>>>> shell: screen -d -m bash /home/dell/tester_server_2/runserver.sh >>>>> >>>>> >>>> But this is not doing the trick >>>> >>>> -- >>>> 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/1ce6131a-3783-48b7-9d3a- >>>> ae837edc1ca5%40googlegroups.com >>>> <https://groups.google.com/d/msgid/ansible-project/1ce6131a-3783-48b7-9d3a-ae837edc1ca5%40googlegroups.com?utm_medium=email&utm_source=footer> >>>> . >>>> >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> >>> -- >> 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] <javascript:>. >> To post to this group, send email to [email protected] >> <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/ansible-project/27d66cd6-019a-4a55-8c1c-52ece7eebe12%40googlegroups.com >> >> <https://groups.google.com/d/msgid/ansible-project/27d66cd6-019a-4a55-8c1c-52ece7eebe12%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> >> For more options, visit https://groups.google.com/d/optout. >> > > -- 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/a550af88-3510-444a-ad02-ee69b9f70032%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
