From mboxrd@z Thu Jan  1 00:00:00 1970
Received: by 10.42.179.196 with SMTP id br4cs285944icb;
        Thu, 2 Dec 2010 05:04:04 -0800 (PST)
Received: by 10.229.185.209 with SMTP id cp17mr8369882qcb.281.1291295044104;
        Thu, 02 Dec 2010 05:04:04 -0800 (PST)
Return-Path: <sup-talk-bounces@rubyforge.org>
Received: from rubyforge.org (rubyforge.org [205.234.109.19])
        by mx.google.com with ESMTP id t30si1216748qcs.107.2010.12.02.05.04.03;
        Thu, 02 Dec 2010 05:04:03 -0800 (PST)
Received-SPF: pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) client-ip=205.234.109.19;
Authentication-Results: mx.google.com; spf=pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-talk-bounces@rubyforge.org
Received: from rubyforge.org (rubyforge.org [127.0.0.1])
	by rubyforge.org (Postfix) with ESMTP id 1F14819783BA;
	Thu,  2 Dec 2010 08:04:03 -0500 (EST)
X-Greylist: delayed 574 seconds by postgrey-1.31 at rubyforge.org;
	Thu, 02 Dec 2010 08:03:53 EST
Received: from vc88.vc.panix.com (vc88.vc.panix.com [166.84.7.88])
	by rubyforge.org (Postfix) with ESMTP id 7D9F41858364
	for <sup-talk@rubyforge.org>; Thu,  2 Dec 2010 08:03:53 -0500 (EST)
Received: from localhost (localhost [127.0.0.1])
	by vc88.vc.panix.com (Postfix) with ESMTP id 005EF1FB5;
	Thu,  2 Dec 2010 12:54:16 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at vc88.vc.panix.com
X-Spam-Flag: NO
X-Spam-Score: -2.91
X-Spam-Level: 
X-Spam-Status: No, score=-2.91 tagged_above=-9999 required=3
	tests=[ALL_TRUSTED=-1.8, BAYES_05=-1.11]
Received: from vc88.vc.panix.com ([127.0.0.1])
	by localhost (vc88.vc.panix.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id LqEIGH8QRaXw; Thu,  2 Dec 2010 12:54:14 +0000 (UTC)
Received: from localhost (host86-154-214-42.range86-154.btcentralplus.com
	[86.154.214.42]) (Authenticated sender: members-iain)
	by vc88.vc.panix.com (Postfix) with ESMTPSA id 0EA8A1DFC;
	Thu,  2 Dec 2010 12:54:12 +0000 (UTC)
From: Iain <rhomunuq+ml_sup@gmail.com>
To: sup-talk <sup-talk@rubyforge.org>
In-reply-to: <AANLkTi=0mcFSCJyJJSqvRuZw60GA9A0aX3MmVRp8hEsP@mail.gmail.com>
References: <AANLkTi=0mcFSCJyJJSqvRuZw60GA9A0aX3MmVRp8hEsP@mail.gmail.com>
Date: Thu, 02 Dec 2010 12:54:11 +0000
Message-Id: <1291294338-sup-7754@leda>
User-Agent: Sup/0.11
Subject: Re: [sup-talk] Can't start Sup, allegedly because of a locked index.
X-BeenThere: sup-talk@rubyforge.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: User & developer discussion of Sup <sup-talk.rubyforge.org>
List-Unsubscribe: <http://rubyforge.org/mailman/options/sup-talk>,
	<mailto:sup-talk-request@rubyforge.org?subject=unsubscribe>
List-Archive: <http://rubyforge.org/pipermail/sup-talk>
List-Post: <mailto:sup-talk@rubyforge.org>
List-Help: <mailto:sup-talk-request@rubyforge.org?subject=help>
List-Subscribe: <http://rubyforge.org/mailman/listinfo/sup-talk>,
	<mailto:sup-talk-request@rubyforge.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sup-talk-bounces@rubyforge.org
Errors-To: sup-talk-bounces@rubyforge.org

> Anyone got any ideas how I get out of this?
> 
> >>>>
> $ sup
> Error: the index is locked by another process! User '' on
> host '' is running  with pid .
> The process was alive as of at least 4216 minutes ago.
> Should I ask that process to kill itself (y/n)? n
> Sorry, couldn't unlock the index.

Something similar happened to me once. I just did "rm ~/.sup/lock", then
started sup as normal. Does that work for you?
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk