ng-cron | Quartz/Unix Cron Component | Cron Utils library

Right. Try to escape that Groovy $ operator (like this \$). So, it comes to Java after compilation as regular symbol. Therefore Spring in the end will be able to resolve that property:

First a few nits:

• Don't specify datetimes with a leading 0 like 06 am because if you edit it to 9am in a rush, you're going to find out that that's not a valid octal number and the whole DAG file will stop parsing.
• You might as well use the pendulum notation: start_date=pendulum.datetime(2018, 12, 11, 6, 0, tz='Pacific/Auckland'),

Yeah timezones in Airflow got a little confusing. The docs say that a cron schedule is always in that timezone's offset. This isn't as clear as it should be because, offsets vary. Lets assume you set the default config timezone like this:

In Google Compute Engine, with an Ubuntu 16.04 VM, the user-level cron jobs don't seem to be kicked off at all; however, root-level jobs work as expected.

Instead of editing crontab like this:

crontab -e

use sudo crontab -e

A simple, working example is * * * * * /usr/bin/python /home/myUserName/test.py to run test.py once a minute.

Airflow support the use of cron expressions. schedule_interval is defined as a DAG arguments, and receives preferably a cron expression as a str, or a datetime.timedelta object. Alternatively, you can also use one of these cron “preset”:None, @once, @hourly, @daily, @weekly , @monthly, @yearly.

As I see, the timezone awareness is correct, but schedule interval should be change.

This is a quick solution that will do exactly what you want without the complicated one-liner:

Create this file in your myaccount -- You may also put it into your bin directory if you so desire just remember where you put it so you can call it from your CRON. Also make sure the user has permissions to read/write to the directory the sh file is in

wget.sh

You should actually take a step back and think what and why you are doing it

Do you need to actually start your long_running program from cron? The reason i ask is that you then write another program(watcher) that starts your long_running program. I hope that you see that yo actually do not need cron to start your long_running program.

So what you have is a watcher firing every minute and starting long_running program if it is not running.

Now you need to actually understand what you are trying to do because there are many ways this can be done. If this is an exercise watcher can call ps and work out from there if it runs and start it. in bash you can do

Your approach above totally over complicates what you are trying to do. You have a php script you want to run at certain intervals throughout the day, sending a few emails each time to people in your database.

Obviously I have no idea what your database looks like, but here's a basic concept.

• Add a column to your email addresses database called sent with default value set to 0
• Write your php script and in your database query use LIMIT = 10 or whatever to only retrieve a few email addresses each time it runs, use WHERE sent = 0 to only retrieve email addresses you havent sent to yet

• Then UPDATE each row to SET sent = 1 after the script has run to mark those users as having already been emailed. Include some conditional code so that if there are no more email addresses for that day WHERE sent = 0 then script just exits.

• Create a cron job to run at your chosen interval which runs your php script and just leave it.

There is no need to delete the cron job, if there are no emails to send it will just run briefly and quit. The whole point of cron jobs is to automate repetitive tasks, you set once and forget. The filters are flexible enough to give you a lot of control over when they run.

For example 0 9-17/2 * * 1-5 php /path/to/script.php would run a script every other hour between 0900 and 1700, Monday to Friday

This does the trick (a little verbose, but works)
You need to set the variable timeStop (HH:MM:SS)

I couldn't find an answer where GitLab will take care of this for me so I just created another cron task: