On Sun, 2004-08-29 at 01:24 -0400, Tom Metro wrote:
http://www.dovecot.org/doc/INSTALL
Once everything is configured, there's two ways to start Dovecot:
Run "dovecot" binary which does everything.
Start it via inetd or similiar by executing "imap-login" or "pop3-login" binaries. If you're listening in SSL port, add --ssl parameter.
What are the pros and cons of using 'dovecot' vs. inetd.
With inetd you can use things like /etc/hosts.allowed and maybe some more advanced features of xinetd and likes. Oh and currently Dovecot doesn't support listening in multiple IPs, but with inetd (or just xinetd?) that's possible.
Downside is that there can't be any preforked login processes waiting for new connections. I'm not sure how useful that is though. Normally it probably gives a few microseconds less latency, but in high load it should help some more.
This may seem silly, but I noticed that there isn't any documentation saying what is the proper way to kill Dovecot. I assume it is to kill the 'dovecot' process. .. Any plans to support a /var/run/dovecot/pid file or similar?
I've been meaning to add support for that, but I've always forgotten that. Yes, I guess I should add that file. Could even make it into 0.99.11 :)
What are your thoughts on including an init.d script in the distribution. I know some of the binary distributions will have platform-specific scripts included, but it might be good to include a generic one for those who build from source.
Does anyone have a platform-independent init.d-script?