2009/2/27 Martin Pala <address@hidden>:
Yes, this is culprit ... it doesn't crash now, but just disables the
resource monitoring because of CPU=0.
I have changed the code to failover to CPU=1 if system reports 0
CPUs.
This way the resource monitoring should be possible again.
The patch is attached - will be part of next monit release
monit-5.0 ...
final should be available during next week.
Martin,
This has fixed my problem. Monit is now up and running once again.
Hooray!
The bug has also been filed against the debian package (it may be a
while before the debian package is upgraded to monit 5).
Many thanks for the help,
Jenny