[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [sup-talk] Can't start Sup, allegedly because of a locked index.

To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Can't start Sup, allegedly because of a locked index.
From: Michael Stapelberg <michael+sup@stapelberg.de>
Date: Thu, 02 Dec 2010 14:00:01 +0100
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
Delivered-to: eg@gaute.vetsj.com
Delivered-to: sup-talk@rubyforge.org
In-reply-to: <AANLkTinRRBOHh=zp3DQXSWvXBnYeABJ6zO1My+SNBfCj@mail.gmail.com>
List-archive: <http://rubyforge.org/pipermail/sup-talk>
List-help: <mailto:sup-talk-request@rubyforge.org?subject=help>
List-id: User & developer discussion of Sup <sup-talk.rubyforge.org>
List-post: <mailto:sup-talk@rubyforge.org>
List-subscribe: <http://rubyforge.org/mailman/listinfo/sup-talk>, <mailto:sup-talk-request@rubyforge.org?subject=subscribe>
List-unsubscribe: <http://rubyforge.org/mailman/options/sup-talk>, <mailto:sup-talk-request@rubyforge.org?subject=unsubscribe>
References: <AANLkTi=0mcFSCJyJJSqvRuZw60GA9A0aX3MmVRp8hEsP@mail.gmail.com> <1291287153-sup-8966@midna.zekjur.net> <AANLkTinRRBOHh=zp3DQXSWvXBnYeABJ6zO1My+SNBfCj@mail.gmail.com>
Sender: sup-talk-bounces@rubyforge.org
User-agent: Sup/git

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

References:
- [sup-talk] Can't start Sup, allegedly because of a locked index.
  - From: Shadowfirebird <shadowfirebird@gmail.com>
- Re: [sup-talk] Can't start Sup, allegedly because of a locked index.
  - From: Michael Stapelberg <michael+sup@stapelberg.de>
- Re: [sup-talk] Can't start Sup, allegedly because of a locked index.
  - From: Shadowfirebird <shadowfirebird@gmail.com>

Prev by Date: Re: [sup-talk] Can't start Sup, allegedly because of a locked index.
Next by Date: [sup-talk] run sup (or sup-sync) as daemon Hello everybody,
Previous by thread: Re: [sup-talk] Can't start Sup, allegedly because of a locked index.
Next by thread: Re: [sup-talk] Can't start Sup, allegedly because of a locked index.
Index(es):
- Date
- Thread