About once a month, bind crashes on my home gateway. I can't provide any
further details than this because there's nothing in the logs, and no core dump
anywhere (possibly because its running inside the chroot ?)
The symptom is that it just stops running for no apparent reason.
Any ideas how I can debug this?
Hm, it isn't easy to debugging. Best way I think could be increase named's debug
level (-d option, number about 20) and move named out from chroot and run it
with selinux protection (selinux protection is more secure than chroot). Outsite
of chroot we could get core dump and find where problem is.. Tell me your decision.
I added -d 20 to the init script, is there a toggle in a config file somewhere
to disable the chroot stuff ?
never mind, I figured it out, I removed it -t from the command line.
Seems to be working for now. I'll open up another bug if it crashes some time.