Absolutes paths for curl & jq about route53-dynamic-dns-with-lambda

[seangreathouse]

Hey chivakaa,
Thanks for your complement and interest in the project.
I'm looking at your suggestion and wondering if the best route is to implement your auto-discovery, or to simply set those paths to variables at the top of the script.
If I implement auto-discovery, I'm using binaries to do it (which and awk in your example)
Is there a reason a system's cron can't find curl, but can find awk or which?
This solution needs to work for everyone.
Thanks in advance for any more thoughts you have on this.

• Sean

[chivakaa]

Hi Sean,

Running script from cron could fail if cron does not load PATH environments where commands / binaries are placed. For instance my root cron has these environments:

HOME=/root
LOGNAME=root
PATH=/usr/bin:/bin
LANG=en_GB.UTF-8
SHELL=/bin/sh
PWD=/root

and because of that some commands are not found and scripts without absolute path can fail. From my point of view at least two possible options to solve the issue:

1. Place all absolute paths for commans inside of scripts invoqued from cron
2. Place PATH definition header on cron (like: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin)

I hope these info can helps!