Ondrej Zajicek <santi...@crfreenet.org> writes: >> Right, yeah, the overflow check is done on the specified values not >> their centisecond equivalents. Oops. > > IMHO the reasonable way would be to keep such values (intervals) > internally in Babel native time units (centiseconds) and only convert > to BIRD units when appropriate (when mixed with bird_clock_t values).
That would work. Also thought about using the expr_us mechanism in the config parser code. However, both of those would break existing configurations (not that there are many at this point; but the principle remains). What is your policy on that? Also, since we can't actually schedule things at a granularity finer than seconds, setting a lower value would just result in announcing deadlines we then cannot meet, which is bound to break things. So for the time being I think keeping it the way it is would be best, no? -Toke
signature.asc
Description: PGP signature
