Tom Horsley writes:
On Sat, 10 Sep 2016 10:20:57 -0400
Sam Varshavchik wrote:
> All-righty, this must be something about this particular named-chroot
> configuration…
In the "check the dumb stuff first" category, might want to
run memtest and check the SMART info on the disk. Always a
chance the code got corrupted somehow and isn't running the
instructions intended to run :-).
I copied the chroot to another server that I can play with. On that one,
named-chroot also segfaults at startup in the same way, so it looks like I
have a weekend project…