djbdns
[Top] [All Lists]

Re: tinydns - softlimit: fatal: out of memory

To: dns@list.cr.yp.to
Subject: Re: tinydns - softlimit: fatal: out of memory
From: Emilio Perea <eperea@walkereng.com>
Date: Mon, 21 May 2007 11:01:38 -0500
Delivered-to: sp-com-lists@consult.net
Delivered-to: gmail-djbdns@securepoint.com
Delivered-to: sp.com.list@gmail.com
Delivered-to: mailing list dns@list.cr.yp.to
In-reply-to: <r02010500-1049-3835963307AD11DC817E000A95ACC382@[192.168.1.101]>
Mail-followup-to: dns@list.cr.yp.to
Mailing-list: contact dns-help@list.cr.yp.to; run by ezmlm
References: <20070521143230.GA4892@hermes.walkereng.com> <r02010500-1049-3835963307AD11DC817E000A95ACC382@[192.168.1.101]>
User-agent: Mutt/1.5.12-2006-07-14
On Mon, May 21, 2007 at 08:09:06AM -0700, ax@ax-im.com wrote:
> I have to admit, I'm puzzled -- this machine isn't all that different
> from the last one I set up, apart from the fact that it's 64-bit Intel
> Xeons instead of Intel Pentiums, so it requires the amd64 OpenBSD
> distro in order to support SMP.

I started to replace a 32-bit AMD Athlon with the dual-core 64-bit
version, but ended up keeping both in different locations.  The older
one is now running 4.1 -stable, but its softlimit has not changed in
over five years.  For the amd64-MP version, the softlimits for tinydns
and axfrdns had to be increased ten times in my case.

I don't understand why, but it doesn't seem to affect anything else.  I
was mistaken about publicfile in my first message -- it is not used on
this pair of servers.

<Prev in Thread] Current Thread [Next in Thread>