ram:
>
> On Mon, 2008-09-22 at 13:03 -0400, Wietse Venema wrote:
> > ram:
> > > My milter is quiet simple. It just does a bsearch on a in-memory array ,
> > > to find if the recipient has blacklisted / whitelisted the sender and
> > > takes action accordingly
> > >
> > > The array now has approx
On Mon, 2008-09-22 at 13:03 -0400, Wietse Venema wrote:
> ram:
> > My milter is quiet simple. It just does a bsearch on a in-memory array ,
> > to find if the recipient has blacklisted / whitelisted the sender and
> > takes action accordingly
> >
> > The array now has approx 200k elements, which
ram:
> My milter is quiet simple. It just does a bsearch on a in-memory array ,
> to find if the recipient has blacklisted / whitelisted the sender and
> takes action accordingly
>
> The array now has approx 200k elements, which should be nothing for
> 4GBRam box
What measures did you take to
On Mon, 2008-09-22 at 08:08 -0400, Wietse Venema wrote:
> ram:
> > I have implemented a custom whitelist/blacklist with a milter. This
> > milter has been working smoothly for a nearly 2 years now on multiple
> > machines
> >
> > But now On 1 machine even if the load is very low and there is am
ram:
> I have implemented a custom whitelist/blacklist with a milter. This
> milter has been working smoothly for a nearly 2 years now on multiple
> machines
>
> But now On 1 machine even if the load is very low and there is ample
> free memory once the number of smtpd processes reaches 300 ( I
I have implemented a custom whitelist/blacklist with a milter. This
milter has been working smoothly for a nearly 2 years now on multiple
machines
But now On 1 machine even if the load is very low and there is ample
free memory once the number of smtpd processes reaches 300 ( I have set
limit to
