On 03/04/2011 11:37 AM, Eric Broch wrote:
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...)
Oh! And, are there any advantages to starting in another way?
---------------------------------------------------------------------------------
I just prefer being consistent with CentOS (and the rest of the world)
rather than using DJB's stuff. ;)
FWIW, the whole init script 'structure' will be changing with COS6, for
the better. System V init is being replaced with Upstart, which was
originally developed for Ubuntu (debian is switching as well). In
addition, sysklogd is being replace with rsyslog. BL, I think it'd be
prudent if QMT were to move in these directions as well. Perhaps v3?
--
-Eric 'shubes'
---------------------------------------------------------------------------------
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
