** Reply to message from "Rick R." <os2-wireless_users@2rosenthals.com> on Sun,
13 Aug 2006 19:40:43 -0700 (PDT)
> ** 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!
I'm woefully short on details, but the gist of the problem is that child (REXX)
programs don't release sockets they open so that if one script calls a second
strip etc. etc. non of the sockets used by the children are released until the
parent closes. I can't tell you if this is common to both classic and object
REXX or just to one of them, but it might be a place to start. Bob Eager
(rde@tavi.co.uk) cna probably give you all the details. The only time I saw it
was when I had a script that was tracking events and running all the time. It
called sub-programs and would eventually crash. Wound up having to kill it
with a cron job then restart it every hour or so until I finally re-wrote the
monitor and children in C. It seems that exiting the parent cleans up very
nicely, but not the sub-programs.
back to list