On Aug 24, 2004, at 4:13 PM, Dossy Shiobara wrote:
This, coupled with the version-specific patches for AOLserver, should fix the 100% CPU utilization issue folks have been seeing.
Out of curiosity, is a similar solution available for nsopenssl-v2.x (for aolserver 3.x)? I see occasions where nsopenssl get stuck in a read/send cycle:
/785: send(31, 0x00000000, 0, 0) = 0 /785: read(31, 0x00AA5100, 5) = 0 /785: send(31, 0x00000000, 0, 0) = 0 /785: read(31, 0x00AA5100, 5) = 0 /785: send(31, 0x00000000, 0, 0) = 0 /785: read(31, 0x00AA5100, 5) = 0 /785: send(31, 0x00000000, 0, 0) = 0 /785: read(31, 0x00AA5100, 5) = 0 /785: send(31, 0x00000000, 0, 0) = 0 /785: read(31, 0x00AA5100, 5) = 0 /785: send(31, 0x00000000, 0, 0) = 0 /785: read(31, 0x00AA5100, 5) = 0 /785: send(31, 0x00000000, 0, 0) = 0 /785: read(31, 0x00AA5100, 5) = 0 /785: send(31, 0x00000000, 0, 0) = 0 /785: read(31, 0x00AA5100, 5) = 0 /785: send(31, 0x00000000, 0, 0) = 0
lsof output shows (sanitized):
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME nsd8x 422 <deleted> 31u IPv4 0x30004a5be38 0t11970 TCP $THISHOST.aol.com:$SSLPORT->spider-dtc-ta012.proxy.aol.com:59397 (CLOSE_WAIT)
Noah Robin System Administrator, America Online
-- AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
