From owner-freebsd-questions@FreeBSD.ORG Sat Jun 27 15:42:26 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1B7CE1065674 for ; Sat, 27 Jun 2009 15:42:26 +0000 (UTC) (envelope-from roberthuff@rcn.com) Received: from smtp02.lnh.mail.rcn.net (smtp02.lnh.mail.rcn.net [207.172.157.102]) by mx1.freebsd.org (Postfix) with ESMTP id C9C508FC1B for ; Sat, 27 Jun 2009 15:42:25 +0000 (UTC) (envelope-from roberthuff@rcn.com) Received: from mr08.lnh.mail.rcn.net ([207.172.157.28]) by smtp02.lnh.mail.rcn.net with ESMTP; 27 Jun 2009 11:42:25 -0400 Received: from smtp01.lnh.mail.rcn.net (smtp01.lnh.mail.rcn.net [207.172.4.11]) by mr08.lnh.mail.rcn.net (MOS 3.10.6-GA) with ESMTP id KYS10870; Sat, 27 Jun 2009 11:42:16 -0400 (EDT) Received: from 209-6-22-188.c3-0.smr-ubr1.sbo-smr.ma.cable.rcn.com (HELO jerusalem.litteratus.org.litteratus.org) ([209.6.22.188]) by smtp01.lnh.mail.rcn.net with ESMTP; 27 Jun 2009 11:42:17 -0400 From: Robert Huff MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <19014.15832.51916.407330@jerusalem.litteratus.org> Date: Sat, 27 Jun 2009 11:42:16 -0400 To: Charles Howse In-Reply-To: References: X-Mailer: VM 7.17 under 21.5 (beta28) "fuki" XEmacs Lucid X-Junkmail-Whitelist: YES (by domain whitelist at mr08.lnh.mail.rcn.net) Cc: FreeBSD Questions Subject: Stale lock files X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Jun 2009 15:42:26 -0000 Charles Howse writes: > What are stale lock files? > I've been having them for a few weeks now, they need to go away! > > root@curly /root# portupgrade -a > ** Stale lock file was found. Removed. > ** Stale lock file was found. Removed. > [...] > > root@curly /root# portversion -c > ** Stale lock file was found. Removed. These are related to a (harmless) twitch in a recent version of ruby. Updating to the latest version fixed it for me. Robert Huff