On 3/11/20 11:20 AM, Sivaraman P wrote:
> & is present in the command to stop so I have used.. it is optional... and
> without & also I have used.. but still it is registering only the first line
>
It should be all there, so for example the following playbook:
---
- hosts: all
tasks:
- c
& is present in the command to stop so I have used.. it is optional... and
without & also I have used.. but still it is registering only the first line
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
To unsubscribe from this group and stop r
On 3/11/20 11:09 AM, Sivaraman P wrote:
> Hi I have the below playbook to stop and start the service using the script
> present in the the target machine,
>
> tasks:
> - name : stop
> command: ./coconf.sh -stop &
> register: stop_details
>
> - debug: var=stop_details
>
> The actual
Hi I have the below playbook to stop and start the service using the script
present in the the target machine,
tasks:
- name : stop
command: ./coconf.sh -stop &
register: stop_details
- debug: var=stop_details
The actual output of stop details contains multiline as below
Using /opt
