On 3/4/2011 10:55 AM, Eric Shubert wrote: > I had a little difficulty with keeping dovecot up at first. It's very > sensitive to time, and I'm running VMs. I think I got the time > situation under control, but I keep this script running as a cron job > every minute just in case: > [root@tacs-mail ~]# cat /usr/local/bin/monitor_dovecot > #!/bin/sh > # check if dovecot's running, and start it if it's not > # shubes - 20090206 - created > service dovecot status >/dev/null 2>&1 || \ > service dovecot start >/dev/null 2>&1 > [root@tacs-mail ~]# > > As you can see, I'm not using supervise for dovecot. I'm not sure > there's really a good reason to do so. (when in Rome...) > Eric,
So, you create the file /etc/rc.d/init.d/dovecot, add it as a service using 'chkconfig --add dovecot' and start it at boot-time using 'chkconfig dovecot on' ? If so, what does you /etc/rc.d/init.d/dovecot file look like? And, as a consequence, I suppose, I would remove /var/qmail/supervise/dovecot/run How do you implement the logging mechanism, through qmailctl and /var/qmail/supervise/dovecot/log/run ? Eric B. --------------------------------------------------------------------------------- Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Vickers Consulting Group offers Qmailtoaster support and installations. If you need professional help with your setup, contact them today! --------------------------------------------------------------------------------- Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com