In a crontab file, the fields are: minute of the hour. hour of the day. day of the month. month of the year. day of the week. So: 10 * * * * blah means execute blah at 10 minutes past every hour. If you want every five minutes, use either: */5 * * * … Read more
Spring Scheduled tasks are not in the same format as cron expressions. They don’t follow the same format as UNIX cron expressions. There are only 6 fields: second, minute, hour, day of month, month, day(s) of week. Asterisk (*) means match any. */X means “every X” (see examples). Numeric days of the week do not … Read more
Run it every three days… 0 0 */3 * * How about that? If you want it to run on specific days of the month, like the 1st, 4th, 7th, etc… then you can just have a conditional in your script that checks for the current day of the month. if (((date(‘j’) – 1) % … Read more
Yeah, yeah, the question is over a year old, but maybe I can add something useful: How to cron something at a random offset 20 times a day between 9am and 11pm? That’s kinda tricky within cron, because you are dividing 14 hours by 20 execution times. I don’t like the other answers very much … Read more
Possibly the easiest way is to simply do three separate jobs: 55 23 30 4,6,9,11 * myjob.sh 55 23 31 1,3,5,7,8,10,12 * myjob.sh 55 23 28 2 * myjob.sh That will run on the 28th of February though, even on leap years so, if that’s a problem, you’ll need to find another way. However, it’s … Read more
I would recommend node-cron. It allows to run tasks using Cron patterns e.g. ‘* * * * * *’ – runs every second ‘*/5 * * * * *’ – runs every 5 seconds ‘10,20,30 * * * * *’ – run at 10th, 20th and 30th second of every minute ‘0 * * * … Read more
You can now set history limits, or disable history altogether, so that failed or successful CronJobs are not kept around indefinitely. See my answer here. Documentation is here. To set the history limits: The .spec.successfulJobsHistoryLimit and .spec.failedJobsHistoryLimit fields are optional. These fields specify how many completed and failed jobs should be kept. By default, they … Read more
You can use BackgroundScheduler() from APScheduler package (v3.5.3): import time import atexit from apscheduler.schedulers.background import BackgroundScheduler def print_date_time(): print(time.strftime(“%A, %d. %B %Y %I:%M:%S %p”)) scheduler = BackgroundScheduler() scheduler.add_job(func=print_date_time, trigger=”interval”, seconds=60) scheduler.start() # Shut down the scheduler when exiting the app atexit.register(lambda: scheduler.shutdown()) Note that two of these schedulers will be launched when Flask is in … Read more
You forgot a *, and you’ve too many fields. It’s the hour you need to care about 0 */6 * * * /path/to/mycommand This means every sixth hour starting from 0, i.e. at hour 0, 6, 12 and 18 which you could write as 0 0,6,12,18 * * * /path/to/mycommand
Run nohup python bgservice.py & to get the script to ignore the hangup signal and keep running. Output will be put in nohup.out. Ideally, you’d run your script with something like supervise so that it can be restarted if (when) it dies.