On 5.10.2004, at 14:12, leon breedt wrote:
It doesn't seem like it crashed though, as closing down Evolution and starting it back up makes it work...its like just that particular connection stops responding. New connections keep on working for other accounts. Don't see any sig11 messages in the logs or any other messages indicating early exit. And CPU utilization looks normal after it stops responding. Couldn't find any coredumps either..
So the connection doesn't actually die immediately, it just doesn't do anything and evolution eventually timeouts it?
Would a complete transcript of all the IMAP commands leading up to this issue help? The service is sitting behind Perdition, so I can log that too.
Maybe. It sounds like there is still something wrong with the new nonblocking writing code..