[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: "for X cycles" has no effect
From: |
jobhunts02 |
Subject: |
Re: "for X cycles" has no effect |
Date: |
Thu, 20 Oct 2016 15:21:20 -0700 |
When I disable logging and change the CPU test to:
"if cpu > 1% for 3 cycles then exec "/usr/bin/logger 'cpu usage exceeded 1%'"
I get the log message after it fails 3 consecutive times. If it then fails a
4th consecutive time, there is no log message. There is not another log
message until the first time it fails after it succeeds, even though it has not
failed 3 consecutive times at that point.
Is this the expected behavior with Monit 5.19.0?
- Re: "for X cycles" has no effect, (continued)
- Re: "for X cycles" has no effect, Paul Theodoropoulos, 2016/10/07
- Re: "for X cycles" has no effect, jobhunts02, 2016/10/07
- Re: "for X cycles" has no effect, jobhunts02, 2016/10/10
- Re: "for X cycles" has no effect, jobhunts02, 2016/10/13
- Re: "for X cycles" has no effect, Martin Pala, 2016/10/17
- Re: "for X cycles" has no effect, jobhunts02, 2016/10/17
- Re: "for X cycles" has no effect, Martin Pala, 2016/10/17
- Re: "for X cycles" has no effect, jobhunts02, 2016/10/18
- Re: "for X cycles" has no effect, Martin Pala, 2016/10/19
Re: "for X cycles" has no effect,
jobhunts02 <=