you are right, Thanks
On Mon, Sep 25, 2017 at 7:42 AM, Brian Coca wrote:
> That was a 'cron tab entry' .. not really an ansible thing, but a cron
> one. Before attempting such a task, you should get familiar with cron.
>
>
>
>
>
> --
> --
> Brian Coca
>
> --
> You
That was a 'cron tab entry' .. not really an ansible thing, but a cron
one. Before attempting such a task, you should get familiar with cron.
--
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
To unsubscribe from
Brian,
Please pardon my question it may sound stupid but i really want to learn
this but dont have a grasp of this yet as i am very new to linux,
where do i place this command " 0 4 * * * /usr/bin/ansible-playbook
/path/to/mybackupplay.yml " is it going to be a file or i run it on
the
ansible-playbook is a 'unix command line utility' you can schedule it
in cron as you would do any other, just pass it the options it needs:
0 4 * * * /usr/bin/ansible-playbook /path/to/mybackupplay.yml
Also, you can make your play an 'executable script' by setting the x
permission bits on
I am newbie at this, i know how to setup ansible playbooks and run them
but i dont know how to schedule a task like backing up cisco configs like
you are trying to do here. I dont know Crontab, how do i set it up and
also does it use scripts as well? Please provide details. thank you!
On
On Wednesday, July 12, 2017 at 6:08:25 PM UTC+2, Brian Coca wrote:
>
> bin/ansible is for Adhoc tasks, you want bin/ansible-playbook is for
> executing playbooks
>
> this makes no sense:
> /usr/bin/ansible /home/ansibleuser/ansible/playbooks/ansible-playbook
> device_bak_2.yml
>
> I think
Thank you so much Brian, it works perfectly.
On Wednesday, July 12, 2017 at 6:08:25 PM UTC+2, Brian Coca wrote:
>
> bin/ansible is for Adhoc tasks, you want bin/ansible-playbook is for
> executing playbooks
>
> this makes no sense:
> /usr/bin/ansible
bin/ansible is for Adhoc tasks, you want bin/ansible-playbook is for
executing playbooks
this makes no sense:
/usr/bin/ansible /home/ansibleuser/ansible/playbooks/ansible-playbook
device_bak_2.yml
I think you want:
/usr/bin/ansible-playbook /home/ansibleuser/ansible/playbooks/device_bak_2.yml
Hi,
I am attempting to schedule a playbook to run every night to backup Cisco
network device configs using crontab.
The playbook is a simple ios_command task executing show run on the Cisco
Devices.
The playbook works fine when I run it manually and I have got to the point
where crontab is