Having trouble with qmail-rspawn (or qmail-lspawn) leaking memory?
One problem is with glibc2.3 (redhat-4) and possibly glibc2.4's implementation of vfork where there is an execvp memory leak in a vfork context described here (https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=221187) and here (http://sources.redhat.com/ml/libc-hacker/2007-01/msg00000.html).
A workaround if you can't get the patch for your system: qmail is stable compiling statically on
a patched system (glibc-2.5.90-15 rawhide or older glibc2.2 system) just add -static to conf-ld and run it on the target system.
Reproduced from http://www.thesmbexchange.com/eng/qmail-rspawn-spawn_memleak.html
See Also a similar report in Qmail Mailing List:
http://www.gossamer-threads.com/lists/qmail/users/131456
I had experienced it and had concluded the same. While searching for this issue reported or experienced by others, I had encountered this post.
Hope that others would also find this useful.
One problem is with glibc2.3 (redhat-4) and possibly glibc2.4's implementation of vfork where there is an execvp memory leak in a vfork context described here (https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=221187) and here (http://sources.redhat.com/ml/libc-hacker/2007-01/msg00000.html).
A workaround if you can't get the patch for your system: qmail is stable compiling statically on
a patched system (glibc-2.5.90-15 rawhide or older glibc2.2 system) just add -static to conf-ld and run it on the target system.
Reproduced from http://www.thesmbexchange.com/eng/qmail-rspawn-spawn_memleak.html
See Also a similar report in Qmail Mailing List:
http://www.gossamer-threads.com/lists/qmail/users/131456
I had experienced it and had concluded the same. While searching for this issue reported or experienced by others, I had encountered this post.
Hope that others would also find this useful.
No comments:
Post a Comment