17 Jun
2021
17 Jun
'21
12:27 a.m.
On 16/06/2021 11:44, ToddAndMargo via users wrote:
On 6/15/21 8:03 PM, Ed Greshko wrote:
In other words, help them to help you by reproducing it and collecting as much relevant data.
If I ever get it figured out, I will report back
OK.... Just as another date point.
I rebuilt the bind-9.16 source for f33. I had named-chroot enabled, and running. I then did "dnf update *rpm" in a directory containing the new version. I then did "systemctl restart named-chroot".
So I have...
[egreshko@f33x ~]$ cat /etc/fedora-release Fedora release 33 (Thirty Three) [egreshko@f33x ~]$ rpm -q bind bind-9.16.16-1.fc33.x86_64
Everything running just fine and the named-chroot service still shows "enabled".
--
Remind me to ignore comments which aren't germane to the thread.