On 26-09-13 15:57, Thomas Raschbacher wrote: > Hi. > > it just happened again: > > read(15, 0xa0d150, 11) = -1 EAGAIN (Resource > temporarily unavailable) > read(15, 0xa0d150, 11) = -1 EAGAIN (Resource > temporarily unavailable)
So read-events on a network socket are being triggered. > #0 0x00007fc2fbf6732a in ci_write () from /usr/lib64/dbmail/libdbmail.so.0 > #1 0x00007fc2fbf6742c in ci_write_cb () from > /usr/lib64/dbmail/libdbmail.so.0 > #2 0x0000000000408018 in imap_cleanup_deferred () But you're also in a deferred cleanup state. During that state, only writes should happen, and only if the connected client can be written to succesfully. Imagine a stdin/stdout connected setup where stdin was closed (EOF) but there is still data pending for stdout. I've pushed a small change that might - hopefully will - help here. http://git.dbmail.eu/paul/dbmail/commit/?h=dbmail_3_1&id=abac5b58c94f270e534320ff264054bc79530b78 If you don't like patching you can pick up a tar-ball there as well. -- ________________________________________________________________ Paul J Stevens pjstevns @ gmail, twitter, github, linkedin * Premium Hosting Services and Web Application Consultancy * www.nfg.nl/i...@nfg.nl/+31.85.877.99.97 ________________________________________________________________ _______________________________________________ DBmail mailing list DBmail@dbmail.org http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
