From: Michael Stapelberg <michael+sup@stapelberg.de>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Can't start Sup, allegedly because of a locked index.
Date: Thu, 02 Dec 2010 14:00:01 +0100 [thread overview]
Message-ID: <1291294755-sup-8801@midna.zekjur.net> (raw)
In-Reply-To: <AANLkTinRRBOHh=zp3DQXSWvXBnYeABJ6zO1My+SNBfCj@mail.gmail.com>
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
next prev parent reply other threads:[~2010-12-02 13:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-02 10:06 Shadowfirebird
2010-12-02 10:53 ` Michael Stapelberg
2010-12-02 12:36 ` Shadowfirebird
2010-12-02 12:56 ` Paul Grove
2010-12-02 13:00 ` Michael Stapelberg [this message]
2010-12-02 12:54 ` Iain
2010-12-02 13:07 ` Shadowfirebird
2010-12-02 13:13 ` David Rysdam
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1291294755-sup-8801@midna.zekjur.net \
--to=michael+sup@stapelberg.de \
--cc=sup-talk@rubyforge.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox