At Tue, 10 Oct 2006 15:14:21 +0200, <attila.bruncsak@...> wrote: > > > > > > > > The new patch breaks our sync mechanism. The sync > > listener thread does > > > > not start before a client connects to the server. > > > > > > > Already first connection from the client at the connect phase > > > (first call back form mlfi_main) will start the sync listener. > > > All the other connections will be blocked on the new mutex > > > which got introduced. There is no any difference with the situation > > > before. > > > > Really? I think the sync_master_restart() call at main() launches > > the master threads and they begin waiting connections from peers. > > > > The sync_master_restart() will be called at the first client connection, > It will do the same stuff as it would be called fron main(). > I do not see problem here. > > > > On the other hand it was neither guaranteed before the patch > > > that the sync listener did any kind of useful thing before client > > > connections came in, since it is not a high priority > > > real-time thread. > > > > I meant we cannot receive sync messages until we receive a mail from > > someone if we apply your second patch. > > > Correct, this is the only difference. We cannot receive sync messages > until someone connects via the sendmail. We cannot receive sync messages until someone connects via the sendmail of ONE OF PEERS. It may happens before your patched server receive a mail.
Message
Re: [milter-greylist] Solution for non executed final_dump()
2006-10-10 by AIDA Shinra
Attachments
- No local attachments were found for this message.