From owner-freebsd-questions@FreeBSD.ORG Sat Jun 27 20:34:06 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 BBAD41065672 for ; Sat, 27 Jun 2009 20:34:06 +0000 (UTC) (envelope-from chowse@charter.net) Received: from mta11.charter.net (mta11.charter.net [216.33.127.80]) by mx1.freebsd.org (Postfix) with ESMTP id 51DF48FC1C for ; Sat, 27 Jun 2009 20:34:06 +0000 (UTC) (envelope-from chowse@charter.net) Received: from imp10 ([10.20.200.10]) by mta11.charter.net (InterMail vM.7.09.01.00 201-2219-108-20080618) with ESMTP id <20090627203405.IZVP22327.mta11.charter.net@imp10>; Sat, 27 Jun 2009 16:34:05 -0400 Received: from larry.local ([24.176.104.69]) by imp10 with smtp.charter.net id 98a51c0061Vr95U058a59z; Sat, 27 Jun 2009 16:34:05 -0400 Message-Id: <511A667D-5CB2-4811-98C2-9F8E7E374B3B@charter.net> From: Charles Howse To: Robert Huff In-Reply-To: <19014.15832.51916.407330@jerusalem.litteratus.org> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v935.3) Date: Sat, 27 Jun 2009 15:34:04 -0500 References: <19014.15832.51916.407330@jerusalem.litteratus.org> X-Mailer: Apple Mail (2.935.3) Cc: FreeBSD Questions Subject: Re: 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 20:34:07 -0000 On Jun 27, 2009, at 10:42 AM, Robert Huff wrote: > > 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. Thanks Robert and Polytropon, Running 'portversion -c' after 'portupgrade -a' no longer shows any stale lock files. Just wondering...is there any utility to find and remove these things? Maybe a reboot?