From mboxrd@z Thu Jan  1 00:00:00 1970
Received: by 10.42.179.196 with SMTP id br4cs287232icb;
        Thu, 2 Dec 2010 05:49:55 -0800 (PST)
Received: by 10.224.179.210 with SMTP id br18mr34693qab.357.1291297795120;
        Thu, 02 Dec 2010 05:49:55 -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 u29si1343989qcp.11.2010.12.02.05.49.54;
        Thu, 02 Dec 2010 05:49:55 -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 B8AE11858364;
	Thu,  2 Dec 2010 08:49:54 -0500 (EST)
Received: from twice-irc.de (mx2.twice-irc.de [79.140.35.195])
	by rubyforge.org (Postfix) with ESMTP id 73EE01858364
	for <sup-talk@rubyforge.org>; Thu,  2 Dec 2010 08:00:03 -0500 (EST)
Received: from midna.zekjur.net (midna.zekjur.net
	[IPv6:2001:4d88:1008:4242:21c:c0ff:fe7e:4776])
	by twice-irc.de (Postfix) with ESMTPSA id 5321A16696E
	for <sup-talk@rubyforge.org>; Thu,  2 Dec 2010 14:00:02 +0100 (CET)
Received: by midna.zekjur.net (Postfix, from userid 101)
	id 0E0DD303837; Thu,  2 Dec 2010 14:00:01 +0100 (CET)
From: Michael Stapelberg <michael+sup@stapelberg.de>
To: sup-talk <sup-talk@rubyforge.org>
In-reply-to: <AANLkTinRRBOHh=zp3DQXSWvXBnYeABJ6zO1My+SNBfCj@mail.gmail.com>
References: <AANLkTi=0mcFSCJyJJSqvRuZw60GA9A0aX3MmVRp8hEsP@mail.gmail.com>
	<1291287153-sup-8966@midna.zekjur.net>
	<AANLkTinRRBOHh=zp3DQXSWvXBnYeABJ6zO1My+SNBfCj@mail.gmail.com>
Date: Thu, 02 Dec 2010 14:00:01 +0100
Message-Id: <1291294755-sup-8801@midna.zekjur.net>
User-Agent: Sup/git
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

Hi Shadowfirebird,

Excerpts from Shadowfirebird's message of 2010-12-02 13:36:21 +0100:
> Relevant last few lines pasted below.   Note, three from the bottom,
> "kill(18723, SIGTERM)".   18723 is the *current* process number, so if I'm
> reading this right, it's self-destructing.
Heh, right. Passing 0 as pid to kill() is not such a good idea.

In your case, I would suggest deleting the lock files manually (use ls -la
.sup/xapian to find them)

Best regards,
Michael
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk