I found a memory leak in the lock() function in the lock.c
source file. Diald allocates memory for the lock_file string
at the begining of the function. The only time the memory is
freed is if diald was unsuccessful in creating a lock file. Every
time diald is successful in bringing the link up and creating a
lock file, more memory is allocated for the lock_file string.
there should be another "free(lock_file);" and "lock_file = NULL;"
statements after the while loop.
I just started using this feature after installing mgetty+sendfax.
mgetty+sendfax monitors the port for any activity. If there is
some traffic on the port, mgetty+sendfax looks for a lock file
to prevent it from interfering with other programs using the port.
I've sent an email to Eric Schenk so hopefully he'll recieve it and
(if I'm correct) issue a new patch for diald.
Brian Chamberlain
[EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
