Cron job to run first Monday each month (SOLVED)

[Indyman]

Hello - I created the cronjob for my Netgear R7000 in an attempt to get it to run the script wol_nas on the first Monday of each month at 7:50pm:
cru a Mon_NAS_on "50 19 1-7 * * [ "$(date '+\%a')" == "Mon"] && /jffs/scripts/wol_nas.sh"
Unfortunately this doesn't work. Also when I execute "cru l" in the router the output is "50 19 1-7 * * [ \Fri == Mon] && /jffs/scripts/wol_nas.sh #Mon_NAS_on#" (note this was run on a Sunday ). What am I missing in my syntax? The wol_nas script should run when the day of the month is between 1-7 and when (date + \%a) = "Mon"? Thanks

 

[Jack Yaz]

Put the date eval in the script with an exit if not a match?

 

[ColinTaylor]

Hello - I created the cronjob for my Netgear R7000 ...

Asuswrt-Merlin is not supported on Netgear hardware. Perhaps you should ask in the Netgear forum.

 

[Jack Yaz]

Asuswrt-Merlin is not supported on Netgear hardware. Perhaps you should ask in the Netgear forum.

Probably the Vortex fork. That being said moving the eval to the script will work, as when adding to cru it's evaluating it at that time, rather than on scheduled call.

 

[ColinTaylor]

Probably the Vortex fork.

Then I say again, not supported. Ask in the XVortex thread.

 

[thelonelycoder]

cru a Mon_NAS_on "50 19 1-7 * * [ "$(date '+\%a')" == "Mon"] && /jffs/scripts/wol_nas.sh"

Try this, runs Mon if day of month is less or equal to 7:

cru a Mon_NAS_on "50 19 * * Mon [ \"\$(date +%d)\" -le 07 ] && /jffs/scripts/wol_nas.sh"

 

[Jack Yaz]

Try this, runs Mon if day of month is less or equal to 7:

cru a Mon_NAS_on "50 19 * * Mon [ \"\$(date +%d)\" -le 07 ] && /jffs/scripts/wol_nas.sh"

Ah, I didn't know escaping characters was a possibility. Makes sense!

 

[thelonelycoder]

Ah, I didn't know escaping characters was a possibility. Makes sense!

Escaping keeps the ", so it can run the evaluation [ "$(date +%d)" -le 07 ].

 

[Indyman]

Asuswrt-Merlin is not supported on Netgear hardware. Perhaps you should ask in the Netgear forum.

Hi Colin - yes I should have been more specific I am using the Xwrt-Vortex port of Merlin's firmware.

 

[Indyman]

Try this, runs Mon if day of month is less or equal to 7:

cru a Mon_NAS_on "50 19 * * Mon [ \"\$(date +%d)\" -le 07 ] && /jffs/scripts/wol_nas.sh"

Hi thelonelycoder - thanks for your response - interesting solution. Wouldn't you need to also escape the %d as well?

 

[Indyman]

Put the date eval in the script with an exit if not a match?

thanks Jack Yaz - yes I would think that would work as well

 

[thelonelycoder]

Hi thelonelycoder - thanks for your response - interesting solution. Wouldn't you need to also escape the %d as well?

Test it, it works as posted.
Remove old job with:

cru d Mon_NAS_on

Then add it with my posted line:

cru a Mon_NAS_on "50 19 * * Mon [ \"\$(date +%d)\" -le 07 ] && /jffs/scripts/wol_nas.sh"

Then check with:

cru l

You'll see:

50 19 * * Mon [ "$(date +%d)" -le 07 ] && /jffs/scripts/wol_nas.sh #Mon_NAS_on#

which is a valid job.

 

[sfx2000]

Remember - there's no RTC, so watch out for reboots and the back to the future impact of the built-in time/data stamp before NTP updates to real time...

 

[thelonelycoder]

Remember - there's no RTC, so watch out for reboots and the back to the future impact of the built-in time/data stamp before NTP updates to real time...

The statement is only run at 19:50 on a Monday. Very unlikely this happens at boot, before NTP kicks in.
Merlin starts at August 1 00:00 and john some other time but far away from 7 PM.

 

[Indyman]

Test it, it works as posted.
Remove old job with:

cru d Mon_NAS_on

Then add it with my posted line:

cru a Mon_NAS_on "50 19 * * Mon [ \"\$(date +%d)\" -le 07 ] && /jffs/scripts/wol_nas.sh"

Then check with:

cru l

You'll see:

50 19 * * Mon [ "$(date +%d)" -le 07 ] && /jffs/scripts/wol_nas.sh #Mon_NAS_on#

which is a valid job.

thelonelycoder - yep looks just like you said with "cru l" - thank you (and hopefully no offense taken)! Looking forward to this running next Monday. Appreciate everyone's responses and helpful comments - thanks again.
Update: the script executed tonite at 7:50PM - woo hoo!