On Wed, 29 Oct 2003, Simon Matter wrote:
> > [EMAIL PROTECTED] wrote:
> >
> >> A simple (maybee) question from an ordinary mailserver admin.....
> >>
> >> I was following Luc's howto when we configured our new mailserver
> >> last week - and we compiled sasl according to his howto like this:
> >>
> >> Sasl 2.1.15
> >> ------------------------------------------------------------------
> >> ./configure \
> >> --enable-anon \
> >> --enable-plain \
> >> --enable-login \
> >> --disable-krb4 \
> >> --with-saslauthd=/var/run/saslauthd \
> >> --with-pam \
> >> --with-dblib=berkeley \
> >> --with-bdb-libdir=/usr/local/bdb/lib \
> >> --with-bdb-incdir=/usr/local/bdb/include \
> >> --with-openssl=/usr/local/ssl \
> >> --with-plugindir=/usr/local/lib/sasl2
> >>
> >> Authentication are done against mysql with pam-mysql and it works
> >> fine, but It turnes out that saslauthd are leaking memory faster than
> >
> > Its actually PAM which is leaking memory. You might be able to work
> > around this problem by adding '-n 0' to your saslatuhd command line.
> >
>
> To be precise, it's a problem of pam_mysql here. Other PAM modules like
> ldap work perfect with saslauthd without leaking.
Uh, we use pam_ldap here with saslauthd and had the same problem with
memory leaks. Using '-n 0' worked great, no performance problems at all.
Andy
