Search Results

However, this may be ill-advised: the file /forcefsck is removed before booting is completed - which means you'll need to automate adding it (e.g. a cron @reboot job) following each reboot. …

Lots of online resources available for "hacking" cron: https://opensource.com/article/17/11/how-use-cron-linux https://en.wikipedia.org/wiki/Cron https://www.raspberrypi.org/documentation/linux/usage/ … cron.md http://www.unixgeeks.org/security/newbie/unix/cron-1.html …

As I understand your question: You have a cron job to reboot your RPi every night at 01:00; e.g. 0 1 * * * sudo reboot (#or something similar; e.g. shutdown -r now) You have a 2nd cron job to restart … your app using the @reboot facility in cron; e.g. …

I would use cron for that job. To employ cron, you only need to add a line to your crontab file. … You can learn more about using cron through a Google search, and by typing man cron and man crontab at the command line. Try this, and if you have specific questions, let us know. …

We can ask cron to tell us what its environment is. … Note also that the user name (aka LOGNAME iaw System V) isn't cron - it's pi! If you're not familiar, with your own user environment, it's useful to compare it against the cron environment. …

In general, there are two approaches: systemd and cron. This answer shows the cron approach. Your question shows the following : sudo python3 /home/pi/videotest.py &. … tries to execute this job cron will sleep for 10 seconds - this gives the system time to get its resources started after 10 seconds, cron will call python3 to run your script located at /home/pi/videotest.py …

You've run into a well-known limitation with cron. The question has been asked and answered here many times. … This recent example highlights the two (at least two) choices you have: use cron (older, simpler) use systemd (newer, more complex) The answer to your question in the context of cron usage is this: …

When you run a command as a cron user, those error messages go "somewhere else", and you don't see them when the script execution is attempted. … It couldn't find it because the cron user has a different $PATH than you do as user pi. …

The explanation as to why cron operates this way, and alternatives to cron are verbose, but have all been documented in this forum. Fortunately, the simple solution is not complicated! … You must simply tell cron to wait a few seconds before it executes your script. …

ANSWER # 3: In the meantime, there is a third alternative to starting your script at boot time: cron. …

However, your cron job does NOT run under your userid, and its stderr stream does NOT go to the screen. … However, cron is (IMHO) simpler, and inserting a sleep command in your crontab will usually resolve resource availability issues. …

"Somewhere else" could be cron - under a user or the root crontabs, or it could be systemd (read man systemctl, and try systemctl list-unit-files). … Absent any other information, I'd have to guess that the solution to your problem is in two steps: Remove the script from ~/.bashrc Create a cron job under the @reboot facility FWIW: rc.local has been …

The version of cron used in Raspbian provides a feature that allows us to start a program when the system boots. … If all this worked, you've just created a cron job that logs each system reboot to a file. …

Once you've verified things are working, create a cron job to run periodically to check your RPi temp and start the fan if it's temperature has exceeded your limit. … This will load your new cron job, and it will execute every minute. Any errors will be written to the file /home/pi/temp-fan.log. …

Here's a suggestion for that bit: Add the command to your crontab, and let cron run it for you at any interval you specify. … In pico (or whatever your default editor is), add a line to tell cron your schedule. In your case, adding the following crontab entry will run your command every minute. …