From owner-freebsd-ports Tue Jul 13 17:10: 5 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 60C8415157 for ; Tue, 13 Jul 1999 17:10:03 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id RAA53438; Tue, 13 Jul 1999 17:10:03 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Date: Tue, 13 Jul 1999 17:10:03 -0700 (PDT) Message-Id: <199907140010.RAA53438@freefall.freebsd.org> To: freebsd-ports@FreeBSD.org Cc: From: Sheldon Hearn Subject: Re: ports/12596: pidentd is unstable in 3.2 and 4.0 Reply-To: Sheldon Hearn 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 To: Kevin Day 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:04:22 +0200 On Sun, 11 Jul 1999 13:29:45 EST, Kevin Day wrote: > # ident /usr/sbin/inetd > /usr/sbin/inetd: > $Id: inetd.c,v 1.48 1999/04/11 09:22:17 markm Exp $ As I suspected, the behaviour you're attributing to pidentd is in fact caused by a buggy inetd. If you're running 3.2-STABLE, you should have inetd.c rev 1.46.2.3 . If you're running 4.0-CURRENT, you should have inetd.c rev 1.59 (although 1.51 ought to do fine if you're holding back for some reason). Make sure you have a suitably up-to-date Makefile and inetd.8 as well. If you're running 4.0-CURRENT, you should also be aware of changes made to etc/defaults/rc.conf to handle recent changes. A good starting point for discussion relevant to the bug you're seeing can be found on PR 12097. Let me know when I can close your PR. :-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message