From owner-freebsd-current  Wed Mar 27 02:32:12 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id CAA17283
          for current-outgoing; Wed, 27 Mar 1996 02:32:12 -0800 (PST)
Received: from time.cdrom.com (time.cdrom.com [204.216.27.226])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id CAA17222
          Wed, 27 Mar 1996 02:32:00 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with SMTP id CAA04150; Wed, 27 Mar 1996 02:31:50 -0800 (PST)
To: "matthew c. mead" <mmead@Glock.COM>
cc: current@FreeBSD.org, ports@FreeBSD.org
Subject: Re: pidentd 
In-reply-to: Your message of "Tue, 26 Mar 1996 19:36:02 EST."
             <199603270036.TAA00490@neon.Glock.COM> 
Date: Wed, 27 Mar 1996 02:31:50 -0800
Message-ID: <4148.827922710@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-current@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

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
proven difficult.

					Jordan

>     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...
> 
> 
> 
> -matt
> 
> -- 
> Matthew C. Mead
> 
> mmead@Glock.COM
> http://www.Glock.COM/~mmead/