pidentd has been proken for ages in exactly this way - I saw bug
reports of it looping at least 2-3 months ago. The only person I know
who runs it is also 100 miles away, so diagnosing the problem has
> Something that's changed recently broke pidentd such that it
> sits and spins off 100% cpu time, and a -current supped this
> afternoon cannot build the -current port of pidentd. Just fyi...
> Matthew C. Mead