[SOLVED] bash script works from command line but not crontab?
ProgrammingThis forum is for all programming questions.
The question does not have to be directly related to Linux and any language is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
If I may add a question:
When you run it from crontab, is it the SAME users crontab that executes it on the command line?
You never answered this question, and I believe wpeckham's on to your solution here. If you're running it from the system wide crontab, it is not going to execute as you expect.
Any particular reason you need to run this script as root? Also, if it's in crontab, how's the sudo getting authorization? Is /etc/sudoers set up properly? Again, does this script really need to be run as root?
Distribution: Raspbian, Mint 13, Slackware 14, Debian & Ubuntu
Posts: 97
Original Poster
Rep:
That was what I understood was needed. The ssh-keygen was run on the same machine, namely 192.168.0.11 and I am expecting data from 192.168.0.12 & 192.168.0.13 & 192.168.0.14.
cron is running as pi ON 192.168.0.11.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.