From owner-freebsd-doc@FreeBSD.ORG Thu Aug 26 06:30:30 2004 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6F25E16A4CE for ; Thu, 26 Aug 2004 06:30:30 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 63A8743D5F for ; Thu, 26 Aug 2004 06:30:30 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.11/8.12.11) with ESMTP id i7Q6UUjv030110 for ; Thu, 26 Aug 2004 06:30:30 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.11/8.12.11/Submit) id i7Q6UTgn030108; Thu, 26 Aug 2004 06:30:29 GMT (envelope-from gnats) Date: Thu, 26 Aug 2004 06:30:29 GMT Message-Id: <200408260630.i7Q6UTgn030108@freefall.freebsd.org> To: freebsd-doc@FreeBSD.org From: Ruslan Ermilov Subject: Re: docs/33645: k5list(1) contains many incorrect "klist" entries. X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Ruslan Ermilov List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Aug 2004 06:30:30 -0000 The following reply was made to PR docs/33645; it has been noted by GNATS. From: Ruslan Ermilov To: Mark Linimon Cc: rdm@cfcl.com, assar@freebsd.org, bug-followup@freebsd.org Subject: Re: docs/33645: k5list(1) contains many incorrect "klist" entries. Date: Thu, 26 Aug 2004 09:25:33 +0300 On Thu, Aug 26, 2004 at 03:06:23AM +0000, Mark Linimon wrote: > Synopsis: k5list(1) contains many incorrect "klist" entries. > > State-Changed-From-To: open->feedback > State-Changed-By: linimon > State-Changed-When: Thu Aug 26 03:06:07 GMT 2004 > State-Changed-Why: > Is this still a problem with modern versions of FreeBSD? > It's no longer a problem in HEAD and RELENG_5, since KerberosIV deorbit. It's still a problem in RELENG_4, but it's unlikely that this will get fixed, so I suggest just closing this PR. Cheers, -- Ruslan Ermilov ru@FreeBSD.org FreeBSD committer