DougieLawson may be correct but what he has suggested looks to me like an educated guess.
The very first thing you need to do is find the error being thrown. That means changing your crontab entry toReboot then check the contents of /tmp/cron.log.
Once you have the error we can stop guessing.
For more on troubleshooting cron and alternative ways to run your script at start up see Cron – A Beginner's Guide and Running A Program At Start Up A Beginner's Guide.
And remember, if you put that into root's* crontab not your normal user's ~ will be expanded to the wrong thing.
*: or any other user's for that matter.
The very first thing you need to do is find the error being thrown. That means changing your crontab entry to
Code:
@reboot cd ~/op25/op25/gr-op25_repeater/apps >/tmp/cron.log 2>&1 && ./op25.sh >>/tmp/cron.log 2>&1Once you have the error we can stop guessing.
For more on troubleshooting cron and alternative ways to run your script at start up see Cron – A Beginner's Guide and Running A Program At Start Up A Beginner's Guide.
And remember, if you put that into root's* crontab not your normal user's ~ will be expanded to the wrong thing.
*: or any other user's for that matter.
Statistics: Posted by thagrol — Thu Mar 21, 2024 6:35 pm