×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Hi Alan,
On 5/26/2016 5:50 PM, Alan Campin wrote:
As to the memory leak I am not clear as to why in the example C programs
that IBM provides for socket servers and socket workers I don't see
anything about freeing the memory.
After they run the spawn, they do a close on the socket id. Is this freeing
the memory or do the IBM examples have a memory leak also?
I've already explained twice in prior messages that I am referring to
saving the pid of the child process and passing it to wait() or
waitpid() to free up the memory. Surely you can see that this isn't the
same thing as closing a socket?!
I don't know which IBM examples you are referring to? The IBM example
linked to from the spawn() manual page does indeed do this.
Maybe you'll believe me if you see where IBM mentions this? It uses the
term "resources" instead of memory, but it amounts to the same thing.
It's on the following page, you have to scroll all the way down to note
15, under "Usage Notes"
http://www.ibm.com/support/knowledgecenter/ssw_ibm_i_72/apis/spawn.htm
-SK
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
