Created attachment 152487 [details] patch As discussed in the mailthread https://lists.freebsd.org/pipermail/freebsd-ports/2015-February/097905.html the /usr/local/etc/rc.d/dovecot startup script displays noise on startup if dovecot is installed but not set up. The patch avoids the noise (hopefully without side effects).
Auto-assigned to maintainer adamw@FreeBSD.org
A commit references this bug: Author: adamw Date: Mon Feb 2 17:16:13 UTC 2015 New revision: 378311 URL: https://svnweb.freebsd.org/changeset/ports/378311 Log: rc.d/dovecot allows for multiple concurrent dovecot setups, but in doing so runs the dovecot binary against each provided configuration file to obtain configuration data. When the configuration file doesn't exist, it says: doveconf: Fatal: open(/im_not_here) failed: No such file or directory Mistyping the conf file locations when doing multiple instances deserves an error message. The real issue here is that in order to set up dovecot, you have to actually copy files over from ${EXAMPLESDIR}. The default configuration file intentionally does not exist in a clean installation. So everybody who installs the dovecot2 port and does not configure it will receive that message at every boot. Fix it with a patch from pi that makes sure the conf file exists before trying to do stuff with it. PORTREVISION bump. PR: 197275 Submitted by: pi Changes: head/mail/dovecot2/Makefile head/mail/dovecot2/files/dovecot.in
Thanks, Kurt! I've committed this patch. That multiple-instances stuff was in there when I inherited the port. Is running multiple instances of dovecot a common thing to do? I definitely don't see other ports doing it... Dovecot lets you set up multiple listeners with per-listener and per-user behaviours, so I'm not sure how useful this is. I'm interested in any thoughts you have here...
Multi-instance setups should become the norm for every kind of daemon, but I have not used it for dovecot yet 8-}