Commit fc8b0e5 (randomization ~) breaks config file

[Seanst3r]

Hi. After cloning the latest git version my crontab won't install. The last commit is this one:

Add random within range '~' operator …
@opohorel opohorel committed on Nov 8, 2021

I get "bad minute", bad "hour", bad day-of-week, you name it.

01 * * * * /bin/echo Hello, world!

crontab: installing new crontab
"/tmp/crontab.ZlLH9I":73: bad minute

I reverted to the prior commit it seems back to normal.

git reset --hard 19c2e1d

[t8m]

Please try the current master branch (07bf4b9)

[Seanst3r]

Ok, I touched my crontab and it installed ok. I can't tell you if it has interpreted it all correctly.. time will tell as my entries fire off but I would assume it will be fine.

As an aside, it's pretty cool that you folks are here maintaining this thing that's been a staple for decades. The fact that someone cared enough to create and share a new feature like this is pretty awesome. I'll be sure to put it to use.

[Seanst3r]

I have to reopen this issue. It seems like the parsing altered by the randomizer code is still messed up.

I wanted a job to run every 5 minutes.

*/5 * * * * whatever
crontab: installing new crontab
"/tmp/crontab.H4l8rU":77: bad minute
Invalid crontab file, can't install.

Workaround was to use a comma separated list of 0,5,10,15 etc.

I get the same thing with hours.

I also noticed that if I use /10 it hangs installing the crontab.

*/10 * * * * whatever

or lets say every 10 hours

• */10 * * * whatever

crontab: installing new crontab
(hang)

[t8m]

@Seanst3r please retest with the latest checkout.