Well, I decided to check into the memory leak problem reported
by some users, and here is the result:
Release LPRng 3.6.20 - Sun Jun 25 16:34:15 PDT 2000
One of the silly memory leaks that has been reported, tested for,
analyzed, etc., finally was found. The problem was in the
child.c file, where I keep track of children processes
by dynamically allocating a list. While I carefully cleaned
up the list in children of the main LPD process,
I never cleaned up the list in the main LPD process. Thus,
if you created a large number of children the list would grow
a small amount (4 bytes) for each child.
This problem was found by brutally using the 'DMALLOC' debugging
package, finding every 'malloc' call in the main LPD process
and then looking for a matching free call in the main line loop.
When one was not found for the case where I had 0 processes
I knew that I had found the problem. Sigh.
-----------------------------------------------------------------------------
If you need help, send email to [EMAIL PROTECTED] (or lprng-requests
or lprng-digest-requests) with the word 'help' in the body. For the impatient,
to subscribe to a list with name LIST, send mail to [EMAIL PROTECTED]
with: | example:
subscribe LIST <mailaddr> | subscribe lprng-digest [EMAIL PROTECTED]
unsubscribe LIST <mailaddr> | unsubscribe lprng [EMAIL PROTECTED]
If you have major problems, send email to [EMAIL PROTECTED] with the word
LPRNGLIST in the SUBJECT line.
-----------------------------------------------------------------------------
