Been using a statically linked bind 4.9.5-P1 for a few months with no
major problems, under Solaris 2.5.1 (with latest "Recommended"
patches applied.)
Noticed some time ago that named on one machine was eating up loads
of CPU for some reason. Restarted it and it was fine.
Today I again noticed the same behaviour on a different machine.
Turned on tracing and found named was spitting out "write failed 32"
thousands of times a second. Although nslookup was still working fine.
Did a named.reload and the beast settled down.
Anyone else seen this? Any fixes? Cheers.
--
Mark Powell - Unix Information Officer - Clifford Whitworth Building
A.I.S., University of Salford, Salford, Manchester, UK.
Tel: +44 161 745 5936 Fax: +44 161 736 3596
<A HREF="http://www.ucsalf.ac.uk/~mark/">Home Page</A>