| Mailing List os2-wireless_users@2rosenthals.com Archived Message #1073 |
back to list |
| From: |
"Rick R." <os2-wireless_users@2rosenthals.com> |
Full Headers
Undecoded message |
| Subject: |
Re: [OS2Wireless] Changed -> SOCKET.SYS crash - REXX Issues |
| Date: |
Sun, 13 Aug 2006 19:40:43 -0700 (PDT) |
| To: |
OS/2 Wireless Users Mailing List <os2-wireless_users@2rosenthals.com> |
|
|---|
** 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.