From owner-freebsd-ports  Tue Jul 13 17:20:40 1999
Delivered-To: freebsd-ports@freebsd.org
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
	by hub.freebsd.org (Postfix) with ESMTP id 3FDDE15360
	for <freebsd-ports@FreeBSD.org>; Tue, 13 Jul 1999 17:20:38 -0700 (PDT)
	(envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.9.3/8.9.2) id RAA54295;
	Tue, 13 Jul 1999 17:20:04 -0700 (PDT)
	(envelope-from gnats@FreeBSD.org)
Date: Tue, 13 Jul 1999 17:20:04 -0700 (PDT)
Message-Id: <199907140020.RAA54295@freefall.freebsd.org>
To: freebsd-ports@FreeBSD.org
Cc: 
From: Sheldon Hearn <sheldonh@uunet.co.za>
Subject: Re: ports/12596: pidentd is unstable in 3.2 and 4.0 
Reply-To: Sheldon Hearn <sheldonh@uunet.co.za>
Sender: owner-freebsd-ports@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

The following reply was made to PR ports/12596; it has been noted by GNATS.

From: Sheldon Hearn <sheldonh@uunet.co.za>
To: Kevin Day <toasty@dragondata.com>
Cc: freebsd-gnats-submit@freebsd.org, green@freebsd.org
Subject: Re: ports/12596: pidentd is unstable in 3.2 and 4.0 
Date: Wed, 14 Jul 1999 02:18:18 +0200

 On Tue, 13 Jul 1999 19:14:26 EST, Kevin Day wrote:
 
 > I can understand the stuck identd processes perhaps, from inetd, but.. I
 > don't see how inetd can make identd return 'no user' when it shouldn't. :)
 
 Well let me know how identd behaves when you have a less buggy inetd.
 :-)
 
 Ciao,
 Sheldon.
 


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message