RE: BIND 9.3.0 coring on SIGHUP (FreeBSD 5.3-RELEASE)

If I remember correctly it was happening in 5.2.1 also.

-----Original Message-----
From: bind-users-bounce@isc.org [mailto:bind-users-bounce@isc.org] On Behalf
Of Robert Lowe
Sent: Wednesday, November 10, 2004 6:32 PM
To: phn@icke-reklam.ipsec.nu; comp-protocols-dns-bind@isc.org
Subject: Re: BIND 9.3.0 coring on SIGHUP (FreeBSD 5.3-RELEASE)

phn@icke-reklam.ipsec.nu wrote:

> Alex R <alex@deviousmeans.net> wrote:
>
>>I compiled BIND 9.3.0 from ports on FreeBSD 5.3-RELEASE and every time =
>
> I
>
>>SIGHUP the server by doing killall -HUP the server cores. When I run na=
>
> med
>
>>in the foreground with -g the server does NOT core but instead I just g=
>
> et:
>
>>09-Nov-2004 13:54:44.569 loading configuration from '/etc/namedb/named.=
>
> conf'
>
>
>>09-Nov-2004 13:54:44.601 ignoring config file logging statement due to =
>
> -g
>
>>option
>
>
>>Has anyone else had this problem or have a solution to it?
>
>
> Never tried SIGHUP since bind-4 days. rndc (rndc stop) is there for a rea=
> son, use it!

SIGHUP was the equivalent of rndc reconfig, IIRC. Stop wasn't even a
concern
before DDNS. Still, the threads issue in FreeBSD 5.3-RELEASE is a bit
disconcerting, assuming the problem did not exist prior to this. What
negative
implications are there in BIND when setting the thread contention scope to
process vs. system? Worse than not having threads at all?

-Robert