Stack Exchange network consists of 183 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.
Visit Stack Exchange
Stack Internal
Knowledge at work
Bring the best of human thought and AI automation together at your work.
Explore Stack Internal The likely cause is that gpio isn't in the PATH available in cron. Specify the full path to your gpio command, such as
getval="$(/sbin/gpio read 17)" Find out where it is on your system using which gpio.
I got bitten by this before because I tinker with embedded solutions a lot. If the script is more complex, I usually initialize PATH and LD_LIBRARY_PATH near the start to make things easier.
The likely cause is that gpio isn't in the PATH available in cron. Specify the full path to your gpio command, such as
getval="$(/sbin/gpio read 17)" I got bitten by this before because I tinker with embedded solutions a lot. If the script is more complex, I usually initialize PATH and LD_LIBRARY_PATH near the start to make things easier.
The likely cause is that gpio isn't in the PATH available in cron. Specify the full path to your gpio command, such as
getval="$(/sbin/gpio read 17)" Find out where it is on your system using which gpio.
I got bitten by this before because I tinker with embedded solutions a lot. If the script is more complex, I usually initialize PATH and LD_LIBRARY_PATH near the start to make things easier.
The likely cause is that gpio isn't in the PATH available in cron. Specify the full path to your gpio command, such as
getval="$(/sbin/gpio read 17)" I got bitten by this before because I tinker with embedded solutions a lot. If the script is more complex, I usually initialize PATH and LD_LIBRARY_PATH near the start to make things easier.