On 25/08/2022 15:54, Ondřej Surý wrote:
I think there's only a risk that ISC doesn't regularly test with older
jemalloc versions,
so you might get a hit by a bug we are not aware of.
Anand, we test regularly on Oracle Linux 7 with jemalloc 3.6.0 from
Oracle's EPEL repository in the CI.
M.
-
Hi Anand,
> I note that none of the official ISC BIND
> packages for EL7 and EL8 link against jemalloc, even though the
> documentation recommends it.
Could you please double check? This is what I get in a fresh CentOS 7
Docker container:
# yum install yum-plugin-copr
# yum copr enable
Hi Ondřej
Thank you for this explanation. I note that none of the official ISC
BIND packages for EL7 and EL8 link against jemalloc, even though the
documentation recommends it.
The jemalloc folks have deemed 3.6 as stable, and that's why it's the
latest version in EPEL7. For EPEL8 and EPEL9,
Hi Anand,
I think there's only a risk that ISC doesn't regularly test with older jemalloc
versions,
so you might get a hit by a bug we are not aware of.
Upstream recommends upgrading to at least 5.1.0 and further releases (up to
5.3.0)
fixes some bugs introduced in 5.x releases, but it's ultima
Dear BIND developers and users,
My question is about jemalloc on Enterprise Linux 7 (RHEL 7 and its
clones). I've built BIND 9.18.6 on CentOS 7. It links against jemalloc
3.6.0, which is available in the EPEL repository.
BIND does run without any problems, but I've only tried it with a
handf
5 matches
Mail list logo
