On 05/10/2010 12:15 AM, Justin Pryzby wrote: > That argument assumes that cron's parser hasn't been improved or > fixed, which is inconsistent with this changelog entry: >=20 > * entry.c > - Explicitly check for valid ranges in range values instead of up= stream's > broken approach which misses certain combinations of ranges and= steps. > Closes: #533726 >=20 > Apparently, this upgrading cron across that version may cause some > crontabs that used to run (with unknown behavior) to no longer be run, > and (if my recollection of someone else's description of Debian's cron > behavior are both accurate) later crontabs from the same file ignored, > even though they would've been run before the upgrade.
You have a point there (in fact, the entire crontab would be ignored). My arguments in #555954 don't hold here, so I'm upgrading this to "normal= ". Would would happen now is that cron would log an error to syslog, which means that error most probably will not reach regular users. Christian
signature.asc
Description: OpenPGP digital signature
