The following bug has been RESOLVED. ====================================================================== http://www.dbmail.org/mantis/bug_view_advanced_page.php?bug_id=0000226 ====================================================================== Reported By: tmatsuo Assigned To: aaron ====================================================================== Project: DBMail Bug ID: 226 Category: General Reproducibility: always Severity: major Priority: normal Status: resolved Resolution: fixed ====================================================================== Date Submitted: 07-Jul-05 12:22 CEST Last Modified: 22-Aug-05 10:18 CEST ====================================================================== Summary: Pop3d and imapd can't start. Description: Pop3d and imapd can't start sometimes. The message is... server.c,dm_bind_and_listen: Address already in use
In the function 'CreateSocket', the value of conf->socket is undefined. So, sometimes the return value of strlen(conf->socket) is 0. But next time, it's 1 or something. When the return value is more than 1, an unix domain socket is created unintentionally, thus 'bind' call fails. To fix this problem 1. Set config->socket value in the function 'SetConfigItems'. or 2. Initialize config.socket value after definition of 'config' struct. ====================================================================== ---------------------------------------------------------------------- aaron - 23-Jul-05 05:16 CEST ---------------------------------------------------------------------- Should be fixed in SVN now. ---------------------------------------------------------------------- paul - 11-Aug-05 16:50 CEST ---------------------------------------------------------------------- Aaron's fix didn't solve this. I've added config_get_value call for this config item to imapd.c and pop3d.c which hopefully does. Re-opening for now. ---------------------------------------------------------------------- paul - 22-Aug-05 10:18 CEST ---------------------------------------------------------------------- I'm setting this bug to resolved for now, since it appears to be fixed now. Bug History Date Modified Username Field Change ====================================================================== 07-Jul-05 12:22tmatsuo New Bug 23-Jul-05 05:16aaron Bugnote Added: 0000782 23-Jul-05 05:16aaron Assigned To => aaron 23-Jul-05 05:16aaron Resolution open => fixed 23-Jul-05 05:16aaron Status new => resolved 11-Aug-05 16:50paul Bugnote Added: 0000818 11-Aug-05 16:50paul Resolution fixed => reopened 11-Aug-05 16:50paul Status resolved => feedback 22-Aug-05 10:18paul Bugnote Added: 0000851 22-Aug-05 10:18paul Resolution reopened => fixed 22-Aug-05 10:18paul Status feedback => resolved ======================================================================
