From: "Rick R." Received: from mxout4.mailhop.org ([63.208.196.168] verified) by 2rosenthals.com (CommuniGate Pro SMTP 5.0.9) with ESMTP id 287754 for os2-wireless_users@2rosenthals.com; Sun, 13 Aug 2006 22:40:53 -0400 Received: from mxin2.mailhop.org ([63.208.196.176]) by mxout4.mailhop.org with esmtp (Exim 4.51) id 1GCSNl-000KNw-JX for os2-wireless_users@2rosenthals.com; Sun, 13 Aug 2006 22:40:50 -0400 Received: from web60621.mail.yahoo.com ([209.73.178.189]) by mxin2.mailhop.org with smtp (Exim 4.51) id 1GCSNl-000MBI-3r for os2-wireless_users@2rosenthals.com; Sun, 13 Aug 2006 22:40:49 -0400 Received: (qmail 17245 invoked by uid 60001); 14 Aug 2006 02:40:43 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=bDvwzMTcpfYVWwIkaVWmztjp3lwcLGltU/Z0st00IHAX5H/PjRYC1D2ezKcECbEpI/B4tdTNS5UmvrwgD4920f5WRRkSyCv4M3W8xFBkNAMisbrX+Ram6wq1SgHJSARRcDZBw2Ofai1iREAmuw7KvjOl/sktl0nmsudmnJDM7Tk= ; Message-ID: <20060814024043.17243.qmail@web60621.mail.yahoo.com> Received: from [12.155.9.87] by web60621.mail.yahoo.com via HTTP; Sun, 13 Aug 2006 19:40:43 PDT Date: Sun, 13 Aug 2006 19:40:43 -0700 (PDT) Subject: Re: [OS2Wireless] Changed -> SOCKET.SYS crash - REXX Issues To: OS/2 Wireless Users Mailing List In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-1595757138-1155523243=:14026" Content-Transfer-Encoding: 8bit X-Mail-Handler: MailHop by DynDNS X-Spam-Score: -2.5 (--) --0-1595757138-1155523243=:14026 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit ** Reply to message from "Will Honea" >In case it got overlooked, if there is any substantial REXX activity you can easily get the SOCKET.SYS message - REXX has a bad habit of not closing sockets until the top level program is closed. Aha, THANKS FOR THAT INFO (first piece of good info about this one). I didn't know that. I do have several REXX monitoring programs running in the background, to check for system intrusions. monitor file changes and online encryption. I also use REXX cron and HW monitoring tools. All those REXX scripts are very short, but they do run repeatedly. So do you have any details about this REXX & TCP/IP socket issue? Very eagerly awaiting any details you got! --------------------------------- Yahoo! Messenger with Voice. Make PC-to-Phone Calls to the US (and 30+ countries) for 2¢/min or less. --0-1595757138-1155523243=:14026 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: 8bit
** Reply to message from "Will Honea"
 
>In case it got overlooked, if there is any substantial REXX activity you can easily get the SOCKET.SYS message - REXX has a bad habit of not closing sockets until the top level program is closed.
 
Aha, THANKS FOR THAT INFO (first piece of good info about this one).
I didn't know that. I do have several REXX monitoring programs running in the background, to check for system intrusions. monitor file changes and online encryption.
I also use REXX cron and HW monitoring tools.
All those REXX scripts are very short, but they do run repeatedly. So do you have any details about this REXX & TCP/IP socket issue?
Very eagerly awaiting any details you got!

Yahoo! Messenger with Voice. Make PC-to-Phone Calls to the US (and 30+ countries) for 2¢/min or less. --0-1595757138-1155523243=:14026--