--On Monday, July 12, 2004 17:16 -0500 Michael Sims <[EMAIL PROTECTED]> wrote:
As promised, I'm following up to the list on the status of this problem, in case anyone has an issue like this in the future. It does appear to have been caused by our intrusion detection device. Our network manager configured this device to avoid scanning POP3 connections and for the past two weeks I have not seen any more pop3 daemons stuck in the middle of a write(). I may be jinxing myself by saying that the problem is resolved but it certainly appears to be so.
write() to disk or network? if network then sounds like a nasty deadlock in the NIDS. i never did like NIDS that required inserting themselves into the traffic stream.
Thanks a lot to everyone who helped me with this.
--- Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
--
GPG/PGP --> 0xE736BD7E 5144 6A2D 977A 6651 DFBE 1462 E351 88B9 E736 BD7E ---
Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
