Hi,
Here is a scenario...
Two servers: both Debian 3.1 stable. Both running bind 9.2.4.1
installed by apt-get.
One bind runs with -t /var/lib/named (bind's chroot option) while the other does not.
Both name servers are working properly and are performing fine.
The chrooted bind will show 0:00 for processing time from ps -aux , while
the non-chrooted case will show some processing time has elapsed.
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
bind 28356 0.0 1.8 44548 16944 ? Ss 10:02 0:00 /usr/sbin/named -u bind -t /var/lib/named
(The chrooted named server is far more busy as well, so it isn't simply a case
of an idle service.)
I checked the bind chroot howto and don't see anything I've missed.
googling hasn't shown anything related to it thus far and up to
now my LUG hasn't suggested a solution.
My feeling is that I'm missing something in named's dev
(I've got null, random and log) or similar.
--Donald Teed