From owner-freebsd-stable Mon Jan 5 16:20:14 1998 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA00789 for stable-outgoing; Mon, 5 Jan 1998 16:20:14 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from opus.cts.cwu.edu (skynyrd@opus.cts.cwu.edu [198.104.92.71]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA00661 for ; Mon, 5 Jan 1998 16:20:06 -0800 (PST) (envelope-from skynyrd@opus.cts.cwu.edu) Received: from localhost (skynyrd@localhost) by opus.cts.cwu.edu (8.8.8/8.8.7) with SMTP id QAA27458 for ; Mon, 5 Jan 1998 16:19:59 -0800 (PST) (envelope-from skynyrd@opus.cts.cwu.edu) Date: Mon, 5 Jan 1998 16:19:59 -0800 (PST) From: Chris Timmons To: freebsd-stable@freebsd.org Subject: pidentd and 2.2.5-stable upgrades Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I noticed that some of my machines with pidentd's from as recently as 9/97 required a freshly installed pidentd after the 2.2.5-stable upgrade in order for pidentd to work (at least I think this is the scenario, we've noticed it on a couple of machines here.) If you've recently upgraded to 2.2.5-stable and use pidentd you might want to make sure that it still works - if not the most recent version in ports seems to do the trick. -Chris