Hi,
I confirmed this behavior on monit 4.9 on Linux 2.6.x
and monit 4.10.beta1
Using the original block from your email:
# monit -v
monit: Debug: Adding credentials for user 'ogg'.
/etc/monitrc:247: Error: the executable does not exist
'/usr/local/bfrt-monit/scripts/nodeControl'
/etc/monitrc:247: Error: the path '/var/run/bfrt-monit/pid-files/testMat.pid'
used in the TIMESTAMP statement does not exist 'warn'
Using this:
check file testMat_pidfile with path /var/run/monitbug.pid
if changed timestamp 3 times within 12 cycles then exec "/usr/bin/yes"
mode manual
group testGroup
# monit -V
This is monit version 4.10-beta1
Copyright (C) 2000-2007 by the monit project group. All Rights Reserved.
# which yes
/usr/bin/yes
# monit -v
monit: Debug: Adding credentials for user 'ogg'.
/etc/monitrc:247: Error: the path '/var/run/monitbug.pid' used in the
TIMESTAMP statement does not exist '/usr/bin/yes'
So the bug appears to still be there.
One thing that monit -v doesn't seem to print is the version info...
Alex Stewart wrote:
Dear All,
Am I missing something here or do people agree this is not desired
behaviour (if so what is the mechanism for filing a bug report)?
-Alex
check file statement from monitrc file:
------------------------------------------------------------
check file testMat_pidfile with path /var/run/bfrt-monit/pid-files/testMat.pid
if changed timestamp 3 times within 12 cycles then exec
"/usr/local/bfrt-monit/scripts/nodeControl warn"
mode manual
group testGroup
------------------------------------------------------------
--
To unsubscribe:
http://lists.nongnu.org/mailman/listinfo/monit-general
