Re: bind 9.16.2 on centos6

2020-04-19 Thread Carl Byington via bind-users
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Sun, 2020-04-19 at 09:07 +0200, Ondrej Sury wrote: > I would suggest starting with vanilla libuv from sources, or at least > review the patches the RPM applies on top of the RPM. There are none. That rpm is just a wrapper around the stock autocon

Re: bind 9.16.2 on centos6

2020-04-19 Thread Ondřej Surý
Carl, I would suggest starting with vanilla libuv from sources, or at least review the patches the RPM applies on top of the RPM. Also please be aware of https://gitlab.isc.org/isc-projects/bind9/-/blob/v9_16/PLATFORMS.md CentOS 6 reaches EOL in few months, so everyone should plan their upgrad

RE: bind 9.16.2 on centos6

2020-04-18 Thread Gilles Buisson
On our last Centos 6 server, we managed building Bind 9.16.1 with the help of Okay repo (http://repo.okay.com.mx) Installed Packages libuv-debuginfo.x86_64 1:1.9.1-4.el6 @okay libuv-devel.x86_64 1:1.9.1-4.el6 @okay libuv-static.x86_64 1:1.9.1-4.el6 @okay libuv1.x86_64

Re: bind 9.16.2 on centos6

2020-04-18 Thread Carl Byington via bind-users
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 > Is this the same issue previously reported against 9.16.1? That was > apparently resolved by downgrading to libuv 1.35. In my case, I can > try > to upgrade to 1.35. Nope, libuv 1.35.0 does not change the crash. -BEGIN PGP SIGNATURE- Ve