> I recall from quite a while back that people were having problems
> with identd running wild and consuming large percentages of CPU. Was
> any progress ever made fixing this? I recently upgraded a sparc to
> a -current snapshot from Dec 3rd, with a kernel from Feb 14th, and 
> I'm experienceing it very frequently... 

This happens if the kernel in /netbsd is not in sync with that in core.
Under these circumstances, groping through symbols in /netbsd will not
point to the right stuff in the core kernel, and identd tends to get in
a loop over this.