如何安排每月的第一个星期日跑步

maybe use cron.hourly to call another script. That script will then check to see if it's the first sunday of the month and 9am, and if so, run your program. Sounds optimal enough to me :-).

A hacky solution: have your cron job run every Sunday, but have your script check the date as it starts, and exit immediately if the day of the month is > 7...

You need to combine two approaches:

a) Use cron to run a job every Sunday at 9:00am.

 00 09 * * 7     /usr/local/bin/once_a_week

b) At the beginning of once_a_week, compute the date and extract the day of the month via shell, Python, C/C++, ... and test that is within 1 to 7, inclusive. If so, execute the real script; if not, exit silently.

You can put something like this in the crontab file:

00 09 * * 7 [ $(date +\%d) -le 07 ] && /run/your/script

The date +%d gives you the number of the current day, and then you can check if the day is less than or equal to 7. If it is, run your command.

If you run this script only on Sundays, it should mean that it runs only on the first Sunday of the month.

Remember that in the crontab file, the formatting options for the date command should be escaped.

If you don't want cron to run your job everyday or every Sunday you could write a wrapper that will run your code, determine the next first Sunday, and schedule itself to run on that date.

Then schedule that wrapper for the next first Sunday of the month. After that it will handle everything itself.

The code would be something like (emphasis on something...no error checking done):

#! /bin/bash
#We run your code first
/path/to/your/code
#now we find the next day we want to run
nskip=28 #the number of days we want to check into the future
curr_month=`date +"%m"`
new_month=`date --date='$nskip days' +"%m"`
if [[ curr_month = new_month ]]
then
((nskip+=7))
fi
date=`date --date='$nskip days' +"09:00AM %D` #you may need to change the format if you use another scheduler
#schedule the job using "at"
at -m $date < /path/to/wrapper/code

The logic is simple to find the next first Sunday. Since we start on the first Sunday of the current month, adding 28 will either put us on the last Sunday of the current month or the first Sunday of the next month. If it is the current month, we increment to the next Sunday (which will be in the first week of the next month).

And I used "at". I don't know if that is cheating. The main idea though is finding the next first Sunday. You can substitute whatever scheduler you want after that, since you know the date and time you want to run the job (a different scheduler may need a different syntax for the date, though).

00 09 1-7 * 0 /usr/local/bin/once_a_week

every sunday of first 7 days of the month

This also works with names of the weekdays:

0 0 1-7 * * [ "$(date '+\%a')" == "Sun" ] && /usr/local/bin/urscript.sh

But,

[ "$(date '+\%a')" == "Sun" ] && echo SUNDAY

will FAIL on comandline due to special treatment of "%" in crontab (also valid for https://stackoverflow.com/a/3242169/2919695)

Run a cron task 1st monday, 3rd tuesday, last sunday, anything..

http://xr09.github.io/cron-last-sunday/

Just put the run-if-today script in the path and use it with cron.

30 6 * * 6 root run-if-today 1 Sat && /root/myfirstsaturdaybackup.sh

The run-if-today script will only return 0 (bash value for True) if it's the right date.

EDIT:

Now with simpler interface, just one parameter for week number.

# run every first saturday
30 6 * * 6 root run-if-today 1 && /root/myfirstsaturdaybackup.sh


# run every last sunday
30 6 * * 7 root run-if-today L && /root/lastsunday.sh

try the following

0 15 10 ? * 1#1

http://www.quartz-scheduler.org/documentation/quartz-1.x/tutorials/crontrigger

It's worth noting that what looks like the most obvious approach to this problem does not work.

You might think that you could just write a crontab entry that specifies the day-of-week as 0 (for Sunday) and the day-of-month as 1-7, like this...

# This does NOT work.
0 9 1-7 * 0 /path/to/your/script

... but, due to an eccentricity of how Cron handles crontab lines with both a day-of-week and day-of-month specified, this won't work, and will in fact run on the 1st, 2nd, 3rd, 4th, 5th, 6th, and 7th of the month (regardless of what day of the week they are) and on every Sunday of the month.

This is why you see the recommendation of using a [ ... ] check with date to set up a rule like this - either specifying the day-of-week in the crontab and using [ and date to check that the day-of-month is <=7 before running the script, as shown in the accepted answer, or specifying the day-of-month range in the crontab and using [ and date to check the day-of-week before running, like this:

# This DOES work.
0 9 1-7 * * [ $(date +\%u) = 7 ] && /path/to/your/script

Some best practices to keep in mind if you'd like to ensure that your crontab line will work regardless of what OS you're using it on:

• Use =, not ==, for the comparison. It's more portable, since not all shells use an implementation of [ that supports the == operator.
• Use the %u specifier to date to get the day-of-week as a number, not the %a operator, because %a gives different results depending upon the locale date is being run in.
• Just use date, not /bin/date or /usr/bin/date, since the date utility has different locations on different systems.

There is a hacky way to do this with a classic (Vixie, Debian) cron:

0 9 1-7 * */7

The day-of-week field starts with a star (*), and so cron considers it "unrestricted" and uses the AND logic between the day-of-month and the day-of-week fields.

*/7 means "every 7 days starting from weekday 0 (Sunday)". Effectively, this means "every Sunday".

Here's my article with more details: Schedule Cronjob for the First Monday of Every Month, the Funky Way

Note – it's a hack. If you use this expression, make sure to document it to avoid confusion later.