UNIX for Dummies Questions & Answers

exacly what I was going to post, good to see a simple answer.

many people over think cron stuff...

IMHO This crontab example illustrates the classic mistake in a crontab entry whereby crontab entries are assumed to be a cumulative exclusive filter when they are not. This one will fire every Sunday AND whenever the day is 22-28.

In my timezone it's Friday 20th. As it happens the 22nd is a Sunday. Let's see if this cron will fire on Mon 23rd, Tue 24th, Wed 25th .... .

well, you were right, it fired last night.

So where did I go wrong?

i found this while searching around... will this work?

1 0 22-28 * * test 'date +\%a' != Sun || /path/to/script >/dev/null 2>&1

---------- Post updated at 10:32 AM ---------- Previous update was at 09:47 AM ----------

Or would it be
1 0 22-28 * * test 'date +\%a' != Sun && /path/to/script >/dev/null 2>&1

I forget...

I dont know... I would never put a test on a cron line...
Truly the test should be in the script you want to be executed...
But that said, it is the correct way: you calculate the interval you know the sunday you want, cron will run during that period, so you test after on the day ( if not sunday, exit...)

All the best

---------- Post updated at 17:58 ---------- Previous update was at 17:33 ----------

Should be:

Code:

test $(date +\%a) = Sun  && ...

Tried that with the &&

test $(date +\%a) != Sun || ...

seems to work

Thanks for the help... but you are right.... we are not going to put that in the cron but rather in the script and just run it in the 4th week range