Re: named coredumping

2005-07-01 Thread Gleb Smirnoff
On Thu, Jun 30, 2005 at 12:57:32PM -0500, Doug Barton wrote: D> FYI, I had a chat with the ISC folks this week, and they said in clear terms D> that enabling threads on current versions of BIND would be a pessimization. D> I have already turned off threads in the port of 9.3.1, and am looking at D>

Re: named coredumping

2005-06-30 Thread Doug Barton
FYI, I had a chat with the ISC folks this week, and they said in clear terms that enabling threads on current versions of BIND would be a pessimization. I have already turned off threads in the port of 9.3.1, and am looking at doing that for the base as well. Could you give the port a try for now

Re: named coredumping

2005-06-22 Thread Gleb Smirnoff
On Tue, Jun 21, 2005 at 10:17:04AM -0700, Doug Barton wrote: D> > D> Thanks for clarifying guys. Are either of you in a position to upgrade to D> > D> -stable and see if the problem persists? D> > D> > Does STABLE have an other version of BIND? D> D> Not newer than 5.4, no, but it does have othe

Re: named coredumping

2005-06-21 Thread Doug Barton
Gleb Smirnoff wrote: > On Mon, Jun 20, 2005 at 11:02:57AM +0200, Doug Barton wrote: > D> Thanks for clarifying guys. Are either of you in a position to upgrade to > D> -stable and see if the problem persists? > > Does STABLE have an other version of BIND? > Not newer than 5.4, no, but it does ha

Re: named coredumping

2005-06-20 Thread Gleb Smirnoff
On Mon, Jun 20, 2005 at 11:02:57AM +0200, Doug Barton wrote: D> Thanks for clarifying guys. Are either of you in a position to upgrade to D> -stable and see if the problem persists? Does STABLE have an other version of BIND? -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE

Re: named coredumping

2005-06-20 Thread Mark Sergeant
On 21/06/2005, at 1:16 AM, Danny Cooper wrote: I am receiving the same problems with FreeBSD 5.4-RELEASE (amd64) bind-9.3.1 DELL PE2850 2 x Intel(R) Xeon(TM) CPU 3.20GHz 4 GB RAM named.log.0:19-Jun-2005 11:46:15.945 *** POKED TIMER *** named.log.0:19-Jun-2005 18:34:17.314 *** POKED TIMER **

Re: named coredumping

2005-06-20 Thread Doug Barton
Thanks for clarifying guys. Are either of you in a position to upgrade to -stable and see if the problem persists? Doug -- This .signature sanitized for your protection ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/l

Re: named coredumping

2005-06-20 Thread Gleb Smirnoff
On Mon, Jun 20, 2005 at 08:08:59AM -0700, Doug Barton wrote: D> Gleb Smirnoff wrote: D> > Dear colleagues, D> > D> >today I've got problem with named exiting on signal 11. Yes, I've searched D> >archives and found that POKED TIMER is a problem in our threads. D> > D> >Has anyone faced this problem

RE: named coredumping

2005-06-20 Thread Danny Cooper
Doug Barton Sent: 20 June 2005 16:09 To: Gleb Smirnoff Cc: [EMAIL PROTECTED] Subject: Re: named coredumping Gleb Smirnoff wrote: > Dear colleagues, > > today I've got problem with named exiting on signal 11. Yes, I've searched > archives and found that POKED TIMER is a probl

Re: named coredumping

2005-06-20 Thread Doug Barton
Gleb Smirnoff wrote: Dear colleagues, today I've got problem with named exiting on signal 11. Yes, I've searched archives and found that POKED TIMER is a problem in our threads. Has anyone faced this problem and workarounded it? Or may be even fixed it? Is there anywhere detailed description