Why didn't parity check run with these settings?

[oliver]

I have these settings: 

 

I interpret this as "run a parity check midnight of the first Friday of every other month. "

[pjrellum]

I have seen something similar. If you look up the cron schedule that is created from these settings it appears to be incorrect (parsing it on a website, I am no expert on reading these schedules:)) I went back to every 1st of the month, manual changes to the file were overwritten by the gui

[oliver]

6 hours ago, pjrellum said:

I have seen something similar. If you look up the cron schedule that is created from these settings it appears to be incorrect (parsing it on a website, I am no expert on reading these schedules:)) I went back to every 1st of the month, manual changes to the file were overwritten by the gui

 

I'm not an expert on reading crontabs

# Generated parity check schedule:
0 0 1-7 2,4,6,8,10,12 5 /usr/local/sbin/mdcmd check  &> /dev/null || :

 

Accroding to https://crontab.guru/#0_0_1-7_2,4,6,8,10,12_5 , it will run this Friday, but im still not sure why.  

 

“At 00:00 on every day-of-month from 1 through 7 and on Friday in February, April, June, August, October, and December.”

next at 2019-02-15 00:00:00

 

 

 

Edited February 13, 2019 by oliver

[bonienl]

The cron daemon used in Unraid is limited in syntax definition, causing certain schedule settings not to work in Unraid 6.6.6.

 

This is a regression error which is corrected in the upcoming Unraid 6.7.0 version (currently available as RC).

[pjrellum]

Thanks, I thought something like that was the case

[oliver]

8 hours ago, bonienl said:

The cron daemon used in Unraid is limited in syntax definition, causing certain schedule settings not to work in Unraid 6.6.6.

 

This is a regression error which is corrected in the upcoming Unraid 6.7.0 version (currently available as RC).

Thanks for the info!