On Wed, 2 Feb 2005, Michael R Head wrote: > Package: dovecot-imapd > Version: 0.99.13-4 > Severity: important > > The new inetd.conf check doesn't work on my sister.
Condolences to your sister. > This causes dovecot to simply not start anymore on my system. > > I run a pops server, but it's not dovecot, but my imaps server is > dovecot. when dovecot looks to see if I'm running a pops server, it > finds one, and decides not to start my dovecot imap server. > Doh! I did not think of this possibility. > I've just removed the new checks from my /etc/init.d/dovecot, and things > are working again, but I think the check needs to be reworked just a > little. > > Perhaps it should only check inetd for the protocols that it finds in > dovecot.conf? > The check was put in because some people run dovecot from inetd not standalone. So they may not have the right entries. What I can do however is check that the pop3 or imap server started in inetd.conf is actually dovecot. Hmm I suppose there may be some weirdos out their who run dovecot-imapd standalone and dovecot-pop3d from inetd or vice-versa. I'll have to think about what to do for them :-) thanks for the report. -- Jaldhar H. Vyas <[EMAIL PROTECTED]> La Salle Debain - http://www.braincells.com/debian/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
