> On Thu, 7 May 2009, Oliver Stöneberg wrote: > > > When you send a SIGINT (STRG+C) to XMail it might not shutdown > > properly as some threads are still active. You need to send it again > > at least once to get XMail to actually shutdown. It was an > > installation, that was still getting mails and the threads were SMTP > > ones. It appears to me the creation of new threads is not suppressed > > by the signal. > > > > I haven't verified this behavior in 1.25, but it was happening to me > > in 1.24 quite a few times. > > XMail tries to wait for all the threads to have completed their current > task, but there might be some of them in the middle of a lengthy network > operation, so you might end up not getting out soon. >
I am aware of that, but it's not the case with my problem. You send the SIGINT and most of the threads shut down, but there are some left, that still process incoming mails until you send another SIGINT. So if there were just one thread stuck in a network timeout, it should not react to that second SIGINT. It's easy to reproduce with a system, that is getting a lot of traffic (even getting a lot of "thread count" errors as well). I am gonna try to get some more information (running it with -Md is very helpful) for you on this. _______________________________________________ xmail mailing list [email protected] http://xmailserver.org/mailman/listinfo/xmail
