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 * * *
Tell me more
×
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.
|
|
|
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. |
|||||
|
|
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 Does your local documentation even mention this sort of case? Maybe it is legal to have two lists, e.g. |
|||
|
|
