Here's another one. I'm getting "permission denied" errors when the parent process tries to grab the socket again after SIGHUP. Before giving the HUP, the parent process is still running with root privs.
Feb 28 04:41:11 [dbmail/imap4d] server.c,StartServer: starting main service loop Feb 28 04:41:22 [dbmail/imap4d] MainSigHandler(): got signal [1] Feb 28 04:41:22 [dbmail/imap4d] pool.c,manage_stop_children: General stop requested. Killing children.. Feb 28 04:41:22 [dbmail/imap4d] serverchild.c,PerformChildTask: accept failed Feb 28 04:41:22 [dbmail/imap4d] serverchild.c,PerformChildTask: stop requested Feb 28 04:41:22 [dbmail/imap4d] pool.c,child_reg_disconnected: [15908] Feb 28 04:41:22 [dbmail/imap4d] serverchild.c,PerformChildTask: accept failed Feb 28 04:41:22 [dbmail/imap4d] serverchild.c,PerformChildTask: stop requested Feb 28 04:41:22 [dbmail/imap4d] pool.c,child_reg_disconnected: [15910] Feb 28 04:41:24 [dbmail/imap4d] imapd.c,main: server done, restart = [1] Feb 28 04:41:24 [dbmail/imap4d] imapd.c,get_config: reading config [set config items] Feb 28 04:41:24 [dbmail/imap4d] server.c,dm_socket: done Feb 28 04:41:24 [dbmail/imap4d] server.c,dm_bind_and_listen: Permission denied Feb 28 04:41:26 [dbmail/imap4d] imapd.c,main: server has exited, exit status [75] Feb 28 04:41:26 [dbmail/imap4d] imapd.c,main: exit On Tue, 2006-02-28 at 12:51 +0100, Paul J Stevens wrote: > Found it. db_check_connection called from StartServer was being called > before db_connect which load the module. > > Oleg Lapshin wrote: > >>I've just checked in some changes in the server code. SIGHUPs are now > >>handled correctly. Oleg and Aaron, please test and confirm if you don't > >>mind. If this works out, 2.1.4 can be released later this week. > > > > > > No. > > The 1st connect from client to dbmail-imapd works fine, > > but the 2nd - don't at all ;( > > > > (in my environment of course) > > >
