[Date Prev] [Date Index] [Date Next] [Thread Prev] [Thread Index] [Thread Next]

Re: Re: memleak?

Fabien Wernli wernli@in2p3.fr
Fri, 12 Jun 2009 07:20:14 GMT

On Thu, Jun 11, 2009 at 04:28:48PM -0700, Bryan Stansell wrote:
> What version are you using?  I don't want to assume.

conserver: conserver.com version 8.1.16
conserver: default access type `r'
conserver: default escape sequence `^Ec'
conserver: default configuration in `/etc/conserver/conserver.cf'
conserver: default password in `/etc/conserver/conserver.passwd'
conserver: default logfile is `/var/log/conserver/server.log'
conserver: default pidfile is `/var/run/conserver/pid'
conserver: default limit is 16 members per group
conserver: default primary port referenced as `conserver'
conserver: default secondary base port referenced as `0'
conserver: options: dmalloc, libwrap, openssl, pam
conserver: dmalloc version: 5.3.0
conserver: openssl version: OpenSSL 0.9.7a Feb 19 2003
conserver: built with `./configure --with-openssl=/var/tmp/openssl-0.9.7a
--with-libwrap --with-dmalloc --with-pam --prefix=/opt
--sysconfdir=/etc/conserver --with-logfile=/var/log/conserver/server.log

> There's also the --with-dmalloc configure option, which I've used in the
> past to track down and eliminate leaks.  I can't guarantee they're all
> gone, but it was an effort (at one point) to remove any I can find).
> Those additional hooks might come in handy.
> Bloat like this shouldn't happen...so there's definitely a problem
> *somewhere*.

I'll see what I can find out using valgrind, as suggested by Nate