Am Thu, Aug 12, 2021 at 05:03:33PM -0700 schrieb Randy Bush:
> FreeBSD 12.2-RELEASE-p6 GENERIC on amd64
> bind 9.16.19 from binary ports
>
> ok, i was quietly waiting for a fix to magically appear and is hasn't.
I got lot's of crashes after upgrading from 9.16.18 to 9.16.19 too.
In my case it hap
> On 13 Aug 2021, at 15:12, Randy Bush wrote:
>
>> Presumably you are running with `named -u`
>
># grep named /etc/rc.conf
>named_enable=YES
>named_program=/usr/local/sbin/named
>named_conf=/usr/home/dns/named.conf
>named_chrootdir=""
>named_chroot_autoupdate=NO
>n
> Presumably you are running with `named -u`
# grep named /etc/rc.conf
named_enable=YES
named_program=/usr/local/sbin/named
named_conf=/usr/home/dns/named.conf
named_chrootdir=""
named_chroot_autoupdate=NO
named_uid=bind
named_gid=bind
named_wait=YES
named_a
> On 13 Aug 2021, at 10:03, Randy Bush wrote:
>
> FreeBSD 12.2-RELEASE-p6 GENERIC on amd64
> bind 9.16.19 from binary ports
>
> ok, i was quietly waiting for a fix to magically appear and is hasn't.
>
> i am getting 10-20 crashes a day on each of two servers. it is not
> leaving disk flowers;
FreeBSD 12.2-RELEASE-p6 GENERIC on amd64
bind 9.16.19 from binary ports
ok, i was quietly waiting for a fix to magically appear and is hasn't.
i am getting 10-20 crashes a day on each of two servers. it is not
leaving disk flowers; and i see no config option to encourage it to do
so.
randy
---
5 matches
Mail list logo