Hi Callum, yes, the number of cycles option in the test is limited to 64 currently, because we store the service states history in a 64-bit bitmap (64 cycles).
We've updated the documentation, thanks for letting us know :) Cheers, Martin On 06 Oct 2014, at 18:03, Callum Macdonald <[email protected]> wrote: > I use monit to alert on excessive replication delay. It triggers fairly > frequently and resolves itself within an hour or so. I wanted to disable the > erroneous alerts by increasing the number of failed cycles. I tried: > > if status != 0 > for 3600 cycles # Alert if down for 1 hour > > Then I got: > > Error: the number of cycles must be between 1 and 64 '3600' > > Checked the docs but didn't see this maximum of 64 mentioned anywhere. > > Is this 64 a hard limit? Any way to increase it? > > If so, is it worth adding something to the documentation to mention this? > Caught me by surprise. > > Cheers - Callum. > > PS> Continued thanks for a truly useful piece of software. > > -- > Callum Macdonald > > DE: +49 1573 245 1224 > UK: +44 7968 378 810 > US: +1 815 246 2207 > www.callum-macdonald.com > > For avoidance of doubt: This email does not constitute permission to add me > to your mailing list. > > > -- > To unsubscribe: > https://lists.nongnu.org/mailman/listinfo/monit-general -- To unsubscribe: https://lists.nongnu.org/mailman/listinfo/monit-general
