I agree with this assessment. The next 5-minute marker is Min25_30. If Min20_25 were inclusive, then it would overlap with Min25_30 by one minute.
It makes sense when they're considered together, and it's better syntax than Min20_24_59. On Oct 12, 2012, at 10:21 AM, Brad Beyenhof wrote: > On Fri, Oct 12, 2012 at 7:31 AM, Bas van der Vlies <b...@sara.nl> wrote: >> >> When i specify a time class like: >> * Min20_25 >> >> Till which minute is this class valid. Is minute Min25 also valid? >> >> I have written a simple test and it show that Min25 is invalid > > I seems to me that this should be expected. The "Min20_25" class > should be valid for five minutes: from xx:20:00 to xx:25:00. If it > were valid from the beginning of minute 20 through the end of minute > 25, that would actually make it valid for six minutes! (Well, 5 > minutes and 59 seconds.) If cf-execd is running cf-agent every 5 > minutes, you might end up running the test two runs in a row, when > that is clearly not intended. > > -Brad > _______________________________________________ > Help-cfengine mailing list > Help-cfengine@cfengine.org > https://cfengine.org/mailman/listinfo/help-cfengine
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Help-cfengine mailing list Help-cfengine@cfengine.org https://cfengine.org/mailman/listinfo/help-cfengine
