Take the 2-minute tour ×
Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems.. It's 100% free, no registration required.

Is this valid crontab time specification, doing what is expected:

0 22-4 * * *

Or is it necessary to do something like

0 22,23,0,1,2,3,4 * * *
share|improve this question

3 Answers 3

up vote 1 down vote accepted

I've never attempted to use a range like that, and I'm not sure whether it would work. So my first advice would be to test it and see what happens - though probably with a script that only does a log entry or something else innocuous.

Second, for ATT and BSD cron you can't have ranges and lists co-existing, so there you'd either have to list each hour separately or have two lines, one with the range and one with the list.

share|improve this answer
    
Modified question to be valid on ATT/BSD by your answer. I'm actually writing "my" crontab spec in Jenkins job configuration (and will test that tonight with dummy job), but I'm asking here to know what is expected behaviour on Unix/Linux system. –  hyde Mar 7 '13 at 9:53
    
Actually I'd expect it to not work and be pleasantly surprised if it did. But I'd also expect cron to complain if you enter an invalid range. –  Jenny D Mar 7 '13 at 10:06

I had problems running cronjobs over midnight. I ended up putting in two almost identical entries for the scripts involved.

* 22-00 * * * /myscript
* 00-05 * * * /myscript

that seemed to do the trick.
I was experiencing cron failures because of using 22-05, and by process of elimination came up with this solution. Hope that helps someone stuck like me. Raspberry Pi, Raspbian

share|improve this answer
    
Exactly what I was looking for. Thanks. –  dentex Oct 19 at 8:55
    
Just a note, it seems doesn't work with */5, i.e.: */5 00-05 * * * /myscript –  dentex Oct 27 at 11:14

There are a wide range of cron daemons around, unless you tell which exact one you are using (the handling of lists in such corner cases could very well change from a version to the next) there can't be an answer. Best bet is to go with your explicit list. I wouldn't be too suprised if some implementation takes your wrap-around as a weird way of saying 4-22...

Does your local documentation even mention this sort of case? Maybe it is legal to have two lists, e.g. 22-24,1-4?

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.