Depends on what cron implementation you are using. If vixie-cron, you can literally put PATH in the crontab line (not that I really recommend this). If cronie you can put environment variables at the top of crontab files but they apply to all commands there. This also works with vixie-cron.
If your cron is a really old one or extremely basic (or if you want to support basically every cron implementation out there), then you have to create a wrapper script that will be on the crontab line. On the machine type you are targeting man 5 crontab and read all of it. On Tuesday, 24 June 2014 14:40:50 UTC-7, Christine Spang wrote: > > I'm using Ansible 1.6.3 to manage a user-specific crontab. This job runs a > command which, as a part of the script, calls another script located in > /usr/local/bin, which is not in cron's default PATH on Debian systems. > > #Ansible: do something > 0 9 * * * /home/admin/bin/do-something >~/logs/do-something.log 2>&1 > > The script fails because it can't find the command called within > `do-something` in /usr/local/bin. The right way to fix this is to set PATH > in the crontab, but I can't see a way to do that with ansible's cron module. > > What's the right way to solve this with Ansible? > -- 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/c8fde34f-4bf4-4f24-93c5-f3fd32fc373e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
