For what it's worth, just escape the escape & this works:
find /iqstage01/archive/* /iqstage01/error/* -type f -exec gzip {} \\;
On Friday, March 9, 2018 at 2:08:33 PM UTC-5, Adam wrote:
>
> Hi -
>
> I've got a task to manage cronjobs on systems that works perfectly fine
> unless I have the following as the job:
>
> find /iqstage01/archive/* /iqstage01/error/* -type f -exec gzip {} \;
>
> Ansible doesn't like the escape on the semi-colon. Does anyone have any
> ideas why?
>
> Thanks,
> Adam
>
--
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 ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/ansible-project/dc048dd9-9197-452c-a830-94d714cff01a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
