Am 10.06.2013 21:04, schrieb Sebastian Arcus:
On 10/06/13 13:14, Reindl Harald wrote:
Am 10.06.2013 11:45, schrieb Sebastian Arcus:
At the moment, if one of the interfaces specified with "listen=" in dovecot.conf is not up when Dovecot is started, then Dovecot just refuses to start. Is there an option to make Dovecot start anyway, and just use the interface when it becomes available? It is inconvenient to have Dovecot refuse to start during boot because some interface is temporarily not available.
Then again, maybe there is some strong security reasoning behind the way Dovecot behaves at the moment?
the main question is why do you not order the start of your services correctly how should a application bind to a specific interface if it is not up?
The order of services is fine as it is. The problem is that if any of the interfaces Dovecot is supposed to be binding to is missing, Dovecot seems to refuse to start at all
where i work and config servers *i want* the to fail if the config is wrong
instead of just binding to what is available
is not a predictable configuration if you specify ecplicit interfaces
openvpn service for example might have been reconfigured on a different IP
so why the hell to you not config dovecot with "address = *" if you want this
On next reboot, there is no imap server available for any interface
which is good because you recognize something goes wrong and if you want it to listen to "whatis available" avoid configs with specific interfaces
One of the network cards might go faulty. On next reboot - not imap server.
so what - if hardware dies you normally want to know it instead hav eit somehow masqueraded
Exim seems to be happy to start regardless of what is available
dovecot too as any other service if you configure it not explicitly for specific interfaces