Did you run it in foregroun debug mode or ktrace(1) it yet? Turn on
querylog and see if you're getting worked?
~BAS
On Tue, 2 Jan 2007, patrick wrote:
I'm running BIND 9.3.2 on FreeBSD 6.1, and am noticing that it gets
out of control after running for a while.
PIDUID THR PRI NICE SIZERES STATETIME WCPU COMMAND
60480 53 1 1320 195M 194M RUN 41.7H 75.54% named
After restarting it, its CPU usage goes back down to what it should
be, as does its memory usage. I really don't want to babysit this
process, so I'm trying to find the cause of this. I have
max-cache-size set to 150M, as before I turned this on, this
process would just grow and grow until it hit FreeBSD's limit and
would stop responding all together, not to mention eating up as much
CPU time as it could.
I never had this problem at all with BIND 8, and am wondering if
there's something I'm doing wrong with BIND 9 to have this problem?
Has anyone else experienced this?
Any help would be greatly appreciated.
Patrick
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
l8*
-lava (Brian A. Seklecki - Pittsburgh, PA, USA)
http://www.spiritual-machines.org/
...from back in the heady days when helpdesk meant nothing, diskquota
meant everything, and lives could be bought and sold for a couple of pages
of laser printout - and frequently were.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
