From: Iain <rhomunuq+ml_sup@gmail.com>
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 12:54:11 +0000 [thread overview]
Message-ID: <1291294338-sup-7754@leda> (raw)
In-Reply-To: <AANLkTi=0mcFSCJyJJSqvRuZw60GA9A0aX3MmVRp8hEsP@mail.gmail.com>
> 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
next prev parent reply other threads:[~2010-12-02 13:04 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
2010-12-02 12:54 ` Iain [this message]
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=1291294338-sup-7754@leda \
--to=rhomunuq+ml_sup@gmail.com \
--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