this is my imap check config:
check process dbmail-imapd with pidfile /var/run/dbmail/dbmail-imapd.pid
group dbmail
start program = "/etc/init.d/dbmail imapd start"
stop program = "/etc/init.d/dbmail imapd stop"
if failed port 143 protocol imap with timeout 2 seconds within 2
cycles then restart
if failed port 993 type TCPSSL protocol imap with timeout 15 seconds
within 3 cycles then restart
if memory > 1024 MB for 3 cycles then alert
if memory > 1524 MB for 3 cycles then restart
if cpu > 80% for 5 cycles then alert
if cpu > 80% for 15 cycles then restart
if you like I could give you the reset too.
Harald
Am 14.10.2013, 19:35 Uhr, schrieb Harald Leithner
<[email protected]>:
Yes it works without problems, but I'm using it with checking imap and
not cpu usage.
Because dbmail could use up to 100% for some time if you have heavy load
on the server.
Harald
Am 14.10.2013, 19:22 Uhr, schrieb Jorge Bastos <[email protected]>:
Hi Guys,
One +/- offtopic question.
Does anyone use "monit" to kill the dbmail process when it is consuming
more
than 100% cpu (zombie) ?
I'd like feedback if it works as expected without any human
intervention.
Thanks in advanced,
Jorge,
--
Harald Leithner
ITronic
Wiedner Hauptstraße 120-124/5.1, 1050 Wien, Austria
Tel: +43-1-545 0 604
Fax: +43-1-786 23 88 26
Mobil: +43-699-123 78 4 78
Mail: [email protected] | itronic.at
_______________________________________________
DBmail mailing list
[email protected]
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
