Rob Siemborski wrote:
On Tue, 20 Jul 2004, Mohamed Magdi Abbas wrote:
Rob Siemborski wrote:
On Mon, 19 Jul 2004, Andrew Brink wrote:
I have also seen this sasauthd memory leak on a Debian box. A
simple restart always fixes the problem for me too.
When we get reports like this it inevitably turns
On Tue, 2004-07-20 at 10:58, Mohamed Magdi Abbas wrote:
> Rob Siemborski wrote:
> > On Mon, 19 Jul 2004, Andrew Brink wrote:
> >
> >> I have also seen this sasauthd memory leak on a Debian box. A simple
> >> restart always fixes the problem for me too.
> >
> >
> > When we get reports like this
On Tue, 20 Jul 2004, Mohamed Magdi Abbas wrote:
Rob Siemborski wrote:
On Mon, 19 Jul 2004, Andrew Brink wrote:
I have also seen this sasauthd memory leak on a Debian box. A simple
restart always fixes the problem for me too.
When we get reports like this it inevitably turns out to be the PAM mod
Rob Siemborski wrote:
On Mon, 19 Jul 2004, Andrew Brink wrote:
I have also seen this sasauthd memory leak on a Debian box. A simple
restart always fixes the problem for me too.
When we get reports like this it inevitably turns out to be the PAM
module leaking memory, not saslauthd itself.
But t
On Mon, 19 Jul 2004, Andrew Brink wrote:
I have also seen this sasauthd memory leak on a Debian box. A simple
restart always fixes the problem for me too.
When we get reports like this it inevitably turns out to be the PAM module
leaking memory, not saslauthd itself.
-Rob
-=-=-=-=-=-=-=-=-=-=-=
Let me know how that works please. I'm using pam because I pull users
from ldap and the cyrus admin from /etc/passwd, but I'd be interested in
using the ldap mech too. I'm running Debian stable here, but sasl and
cyrus are compiled from source.
Andy
On Mon, 19 Jul 2004, Lenny wrote:
>
Very useful information. Thank you, Igor.
Lenny
--
"Wisdom is to a man an infinite Treasure" - Anonymous"
Quoting Igor Brezac <[EMAIL PROTECTED]>:
On Mon, 19 Jul 2004, Lenny wrote:
Ya, I could do that. Would there be a gain for me to compile the latest from
source and using the ldap mech as opposed
On Mon, 19 Jul 2004, Lenny wrote:
> Ya, I could do that. Would there be a gain for me to compile the latest from
> source and using the ldap mech as opposed to the "-n0" flag suggestion
> that was
> made?
-n0 is very taxing on the OS specially if you have a lot of users.
saslauthd/ldap does not
Ya, I could do that. Would there be a gain for me to compile the latest from
source and using the ldap mech as opposed to the "-n0" flag suggestion
that was
made?
Lenny
--
"Wisdom is to a man an infinite Treasure" - Anonymous"
Quoting Igor Brezac <[EMAIL PROTECTED]>:
On Mon, 19 Jul 2004, Lenny wr
On Mon, 19 Jul 2004, Lenny wrote:
> Fedora Core 1's saslauthd doesn't seem to like me setting the mech to
> ldap. This
> works great on Core 2, but I'm not in a postition to migrate all the cyrus
> servers to Fedora Core 2 as of yet. So this is a temporary problem for me :)
Can you build saslaut
Fedora Core 1's saslauthd doesn't seem to like me setting the mech to
ldap. This
works great on Core 2, but I'm not in a postition to migrate all the cyrus
servers to Fedora Core 2 as of yet. So this is a temporary problem for me :)
Lenny
--
"Wisdom is to a man an infinite Treasure" - Anonymous"
pam is known to leak memory on some OSs. This is really not saslauthd
problem. Have you tried to use saslauthd built-in ldap mech?
-Igor
On Mon, 19 Jul 2004, Lenny wrote:
> Using the pam mech which in turn is authing against an openldap server.
>
> I've tried the -n0 flag that was just mentio
Using the pam mech which in turn is authing against an openldap server.
I've tried the -n0 flag that was just mentioned in hopes this solves
the problem
:)
Lenny
--
"Wisdom is to a man an infinite Treasure" - Anonymous"
Quoting Igor Brezac <[EMAIL PROTECTED]>:
What saslauthd authentication mechan
What saslauthd authentication mechanism are you using?
-Igor
On Mon, 19 Jul 2004, Lenny wrote:
> Not sure about RHEL, but on Fedora Core 1 the saslauthd process eats tons of
> swap until eventually there's no memory left. Great fun! This of course stops
> cyrus from being able to process imap a
Thanks for the tip!
Andrew
-Original Message-
From: Andrew Morgan [mailto:[EMAIL PROTECTED]
Sent: Monday, July 19, 2004 4:31 PM
To: Andrew Brink
Cc: Lenny; Mohamed Magdi Abbas; Cyrus Mailing List
Subject: RE: Virtual Memory Consumption of Cyrus IMAPd
You want to run saslauthd with the
We useta see that at my place of work as well, all the way back into RH7.3,
but *ONLY* on the RedHat systems. nothing else.
--On Monday, July 19, 2004 16:46 -0400 Lenny <[EMAIL PROTECTED]> wrote:
Not sure about RHEL, but on Fedora Core 1 the saslauthd process eats tons
of
swap until eventually t
Mohamed Magdi Abbas
> Cc: Cyrus Mailing List
> Subject: Re: Virtual Memory Consumption of Cyrus IMAPd
>
>
> Not sure about RHEL, but on Fedora Core 1 the saslauthd process eats tons of
> swap until eventually there's no memory left. Great fun! This of course stops
> cyr
List
Subject: Re: Virtual Memory Consumption of Cyrus IMAPd
Not sure about RHEL, but on Fedora Core 1 the saslauthd process eats tons of
swap until eventually there's no memory left. Great fun! This of course stops
cyrus from being able to process imap and pop logins (if you're using
Not sure about RHEL, but on Fedora Core 1 the saslauthd process eats tons of
swap until eventually there's no memory left. Great fun! This of course stops
cyrus from being able to process imap and pop logins (if you're using
saslauthd
for authentication). A simple restart usually fixes this partic
I'm running cyrus impad(v 2.2.6), used to run 2.1.16, on RHEL 3.0 and
noticed that the amount of swap space free is decreasing. When I was
running v2.1.16, the swap free would decrease until the kernel oom(out
of memory) killer would activate and start killing processes which
essentially grinds
20 matches
Mail list logo
