[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[monit-dev] monit CHANGES.txt event.c monit.pod state.c
From: |
Martin Pala |
Subject: |
[monit-dev] monit CHANGES.txt event.c monit.pod state.c |
Date: |
Wed, 15 Oct 2008 20:54:20 +0000 |
CVSROOT: /sources/monit
Module name: monit
Changes by: Martin Pala <martinp> 08/10/15 20:54:20
Modified files:
. : CHANGES.txt event.c monit.pod state.c
Log message:
make the error flag non-persistent across monit restart/reload - the
events are paired with the particular test using action memory address, which
is not persistent across monit restart, thus it's not possible to pair after
reload and reset the flag if the service is OK on monit start with current
design. Not big deal though - if the service will fail again or is still failed
after monit reload, monit will do it's job notmally. The fix just doesn't emmit
alert when the service was in error state before monit stop and recovered
before monit started
CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/monit/CHANGES.txt?cvsroot=monit&r1=1.436&r2=1.437
http://cvs.savannah.gnu.org/viewcvs/monit/event.c?cvsroot=monit&r1=1.81&r2=1.82
http://cvs.savannah.gnu.org/viewcvs/monit/monit.pod?cvsroot=monit&r1=1.237&r2=1.238
http://cvs.savannah.gnu.org/viewcvs/monit/state.c?cvsroot=monit&r1=1.33&r2=1.34
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [monit-dev] monit CHANGES.txt event.c monit.pod state.c,
Martin Pala <=